JP7731455B2 - Payment system, transmission method, and program - Google Patents

Description

This disclosure relates to a payment system, a transmission method, and a program.

Payment services in which users make payments using their user terminals are known. For example, Patent Document 1 describes how, when a user makes a payment using a payment app installed on the user terminal, the payment server selects an investment product based on payment amount information and suggests the purchase of the selected investment product via a finance app, which is a mini-app launched within the payment app.

Japanese Patent Application Laid-Open No. 2022-104128

However, with the technology of Patent Document 1, the payment server selects investment products based on payment amount information, and payment information related to payments is not directly exchanged between the payment app and the finance app. As a result, with the technology of Patent Document 1, the collaboration between the payment app and the finance app is insufficient. This also applies to services that do not use apps. With conventional technology, the collaboration between payment services and related services that are related to the payment service is insufficient.

One of the purposes of this disclosure is to enhance collaboration between payment services and related services.

The payment system disclosed herein includes a payment information acquisition unit that acquires payment information related to a payment when a user using a payment service makes a payment using a user terminal; a transmission unit that transmits the payment information to an associated app of a related service related to the payment service; and a processing execution unit that executes an associated service process for the related service based on the associated app and the payment information transmitted to the associated app.

This disclosure can enhance collaboration between payment services and related services.

FIG. 2 is a diagram illustrating an example of a hardware configuration of a payment system. FIG. 10 is a diagram illustrating an example of a screen displayed on a user terminal. FIG. 1 is a diagram illustrating an example of functions implemented in a payment system. FIG. 2 is a diagram illustrating an example of a user database. FIG. 10 is a diagram illustrating an example of processing executed in the payment system. FIG. 10 is a diagram illustrating an example of processing executed in the payment system. FIG. 10 is a diagram illustrating an example of a function realized in a modified example.

[1. Hardware configuration of payment system]
An example of an embodiment of a payment system, a transmission method, and a program according to the present disclosure will be described. Fig. 1 is a diagram showing an example of the hardware configuration of a payment system. For example, the payment system 1 includes a payment server 10, an associated server 20, a user terminal 30, and a store terminal 40. Each of the payment server 10, the associated server 20, the user terminal 30, and the store terminal 40 is connected to a network N such as the Internet or a LAN.

The payment server 10 is a server computer for a payment service. The payment service is a service that provides users with electronic payments (cashless payments). For example, the payment server 10 includes a control unit 11, a memory unit 12, and a communication unit 13. The control unit 11 includes at least one processor. The memory 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.

The related server 20 is a server computer for related services. Related services are services related to payments. Related services can also be described as services linked to payment services. In other words, related services can be services accessible via a payment app that provides a payment service. In this embodiment, the related services are services provided by a card company that issues a credit card that can be used with the payment service, but the related services may also be other services. For example, the related services may be e-commerce services, online flea market services, travel booking services, communications services, financial services, video streaming services, or other services. For example, the related server 20 includes a control unit 21, a memory unit 22, and a communication unit 23. The hardware configurations of the control unit 21, the memory unit 22, and the communication unit 23 may be similar to those of the control unit 11, the memory unit 12, and the communication unit 13, respectively.

The user terminal 30 is a user's computer. For example, the user terminal 30 is a smartphone, tablet, personal computer, or wearable terminal. The user terminal 30 includes a control unit 31, a memory unit 32, a communication unit 33, an operation unit 34, a display unit 35, and an imaging unit 36. The hardware configurations of the control unit 31, the memory unit 32, and the communication unit 33 may be similar to those of the control unit 11, the memory unit 12, and the communication unit 13, respectively. The operation unit 34 is an input device such as a touch panel or a mouse. The display unit 35 is a display such as an LCD or organic EL. The imaging unit 36 includes at least one camera.

The store terminal 40 is a computer of a store that is a member of the payment service. For example, the store terminal 40 is a POS terminal, handheld terminal, smartphone, tablet, or personal computer. The store terminal 40 includes a control unit 41, a memory unit 42, a communication unit 43, an operation unit 44, a display unit 45, and a reading unit 46. The hardware configurations of the control unit 41, the memory unit 42, the communication unit 43, the operation unit 44, and the display unit 45 may be similar to those of the control unit 11, the memory unit 12, the communication unit 13, the operation unit 34, and the display unit 35, respectively. The reading unit 46 includes at least one code reader or reader/writer. The reading unit 46 may include at least one camera.

The programs stored in the storage units 12, 22, 32, and 42 may be supplied to the payment server 10, the related server 20, the user terminal 30, or the store terminal 40 via the network N. The payment server 10, the related server 20, the user terminal 30, or the store terminal 40 may also include at least one of a reading unit (e.g., a memory card slot) that reads a computer-readable information storage medium and an input/output unit (e.g., a USB port) for inputting and outputting data to and from an external device. For example, a program stored in an information storage medium may be supplied to the payment server 10, the related server 20, the user terminal 30, or the store terminal 40 via at least one of the reading unit and the input/output unit.

Furthermore, the payment system 1 only needs to include at least one computer. The computers included in the payment system 1 are not limited to the example shown in Figure 1. For example, the payment system 1 may include only the payment server 10 and the user terminal 30. In this case, the related server 20 and the store terminal 40 exist outside the payment system 1. The payment system 1 may also include only the payment server 10. In this case, the related server 20, the user terminal 30, and the store terminal 40 exist outside the payment system 1. For example, the payment system 1 may also include the payment server 10 and another computer not shown in Figure 1. The payment system 1 may also include only the user terminal 30. In this case, the payment server 10, the related server 20, and the store terminal 40 exist outside the payment system 1.

[2. Overview of the payment system]
In this embodiment, a user operates a user terminal 30 to use a payment service. The user can use any payment method for the payment service. A payment method is a method used by a user for payment. For example, a payment method may be a credit card, electronic money, points, cryptocurrency, a debit card, a wallet, an account such as a bank account, or other methods. Codes such as barcodes or two-dimensional codes are also methods for payment and therefore correspond to a payment method. A payment method can also be called a payment means.

In this embodiment, an example is given of a case where a user makes a payment using a payment app installed on the user terminal 30. The payment app is an application provided by a business operator that operates a payment service. Once the user installs the payment app on the user terminal 30 and registers as a member of the payment service, they can use the payment service. Once the user has registered as a member and launched the payment app, the user terminal 30 displays the top screen of the payment app on the display unit 35. The top screen is the first screen that is displayed after the payment app is launched. The top screen is sometimes called the first view.

Figure 2 is a diagram showing an example of a screen displayed on the user terminal 30. For example, when the payment app is launched, as shown in the upper left of Figure 2, the user terminal 30 displays on the display unit 35 a top screen SC1 including a code C10 generated based on a code ID that can temporarily identify the user. The code C10 is at least one of a barcode and a two-dimensional code. When the code C10 is read by the reading unit 46 of the store terminal 40, payment is executed based on the code ID obtained from the code C10. In the example of Figure 2, a credit card is set as the payment source, so payment is executed based on the credit card. The payment process may be a known process.

Note that payment is not limited to the type in which the store terminal 40 reads the code C10 displayed on the user terminal 30. Payment may be of any type. For example, payment may be of the type in which the user terminal 30 reads a code displayed on the store terminal 40, the type in which the user terminal 30 reads a code posted in the store, the type completed by operating the user terminal 30 alone (e.g., ID payment or account payment), the type in which the IC chip in the user terminal 30 is used, carrier payment which is payment by the carrier used by the user terminal 30, or any other type.

In this embodiment, depending on the payment amount, an installment payment app for later installment payments is suggested to the user on the payment completion screen SC2, which indicates that the payment has been completed. The installment payment app is an application provided by the card company of the credit card used for the payment. In this embodiment, an example is given in which the payment app is a super app and the installment payment app is a mini app. The super app is an app that manages multiple mini apps. The mini apps are apps that are called from the super app.

In this embodiment, mini apps include apps that operate based on the payment app as a super app, but also include apps that transition to apps provided by the related server 20 via the payment app, as in the modified example described below. Furthermore, mini apps may also include apps that transition to website screen displays, etc. via the payment app. As shown in the upper left of Figure 2, the top screen SC1 includes an app list L11 that displays a list of mini apps. Such links may correspond to mini apps.

Furthermore, an integrated app that integrates a payment app with an installment payment app, which is an example of an associated app, may be installed on the user terminal 30. The portion of the integrated app that provides payment services to the user may be the payment app, and the portion that provides associated services to the user may correspond to the associated app. For example, smartphone apps are often not a single program, but a collection of many small programs (for example, programs that correspond to subroutines called from a main routine). The concept that encompasses many programs is an integrated app, and the small programs within that may be the payment app and the associated app.

For example, a user can launch an installment payment app from the app list L11 on the top screen SC1, but for large payments, the installment payment app can be launched directly from the payment completion screen SC2. If the user's payment amount is equal to or greater than a threshold, the user terminal 30 displays the payment completion screen SC2 on the display unit 35, including app information I20 indicating the installment payment app, as shown in the upper right corner of Figure 2. Users who have made large payments may wish to pay in installments, and can therefore proceed with the installment payment procedure directly from the payment completion screen SC2.

For example, when a user selects app information I20 for an installment payment app, as shown in the lower right of Figure 2, the user terminal 30 launches the installment payment app and displays the app screen SC3 for installment payments on the display unit 35. Generally, it may take some time (e.g., several hours to several days) for a payment to be reflected on the screen that manages credit card statements. In this case, the user cannot apply for installment payments until the payment is reflected on the statement.

In this embodiment, therefore, payment information for the payment executed by the payment app is sent from the payment app to the installment payment app. For example, when a user selects app information I20, the payment information for the payment shown on the payment completion screen SC2 is sent from the payment app to the installment payment app. This allows the user terminal 30 to display the app screen SC3 for accepting an installment payment application on the display unit 35 immediately after the payment is made.

On the other hand, if the user's payment amount is below the threshold, the payment amount is low, so the probability that the user will request an installment payment app is low. For this reason, as shown in the lower left of Figure 2, the user terminal 30 displays a payment completion screen SC2 on the display unit 35 that does not include app information I20 for the installment payment app. For example, if the user's payment amount is below the threshold, the payment completion screen SC2 includes other information I21 that shows advertisements for other services, such as e-commerce services. If the user's payment amount is below the threshold, the payment completion screen SC2 may include app information I20 for apps other than the installment payment app (for example, a points app). Note that while the above example illustrates a case in which app information I20 is displayed based on whether the payment amount is below a predetermined threshold, the threshold may also be a payment amount set by the user.

As described above, when a user makes a payment using the user terminal 30, the payment system 1 of this embodiment determines whether the payment amount of the payment is equal to or greater than a threshold. If it is determined that the payment amount of the payment is equal to or greater than the threshold, the payment system 1 displays the app information I20 of the installment payment app on the payment completion screen SC2. When the user selects the app information I20 of the installment payment app, payment information is sent from the payment app to the installment payment app. This enables the payment system 1 to enhance the collaboration between payment services and related services. As a result, the user can apply for installment payments from the app screen SC3 of the installment payment app immediately after making a payment. Details of the payment system 1 are explained below.

[3. Functions realized by the payment system]
3 is a diagram showing an example of functions realized by the payment system 1. The units realized by the payment system 1 can be configured as a single device or as smaller distributed devices.

[3-1. Functions realized by the payment server]
For example, the payment server 10 includes a data storage unit 100, a payment execution unit 101, a payment information acquisition unit 102, an application information acquisition unit 103, and a proposal unit 104. The data storage unit 100 is realized by the memory unit 12. The payment execution unit 101, the payment information acquisition unit 102, the application information acquisition unit 103, and the proposal unit 104 are each realized by the control unit 11.

[Data storage unit]
The data storage unit 100 stores data necessary for the payment service. For example, the data storage unit 100 stores a user database DB.

Figure 4 shows an example of a user database DB. The user database DB is a database that stores various information related to users. For example, the user database DB stores user IDs, passwords, code IDs, payment method information, and payment history information. The user database DB may also store other data. For example, the user database DB may store payment source information related to payment methods set by the user as payment sources, or charging source information related to payment methods set by the user as electronic money charging sources.

The user ID is an example of user identification information that can identify a user. A login account may exist in addition to the user ID. The login account may be freely changeable by the user. The password is information that is confirmed when logging in. The code ID is also an ID that can identify a user in the payment service. The code ID is updated each time the code C10 is displayed.

Payment method information is information that identifies the payment methods that a user can use with a payment service. For example, payment method information is information such as a credit card number, electronic money number, or point card number balance. Payment history information is information related to the user's usage history of the payment service. For example, payment history information indicates the date and time of payment, the payment location, the payment amount, the payment target, or a combination of these. When a user makes a payment, the payment execution unit 101, described below, updates the payment history information to indicate the details of the payment.

Note that the data stored in the data storage unit 100 is not limited to the above example. The data storage unit 100 may store any data necessary for the payment service. For example, the data storage unit 100 may store data for various screens displayed on the payment app.

[Payment Execution Department]
The payment execution unit 101 executes payment in the payment service. The processing for payment may be a known processing. In the case of a type of payment in which the code C10 displayed on the user terminal 30 is read by the store terminal 40, as in this embodiment, the payment execution unit 101 executes payment based on a payment request received from the store terminal 40. The payment execution unit 101 references the user database DB and executes payment based on payment method information associated with the code ID included in the payment request received from the store terminal 40. For example, if the user has set a credit card as the payment source, the payment execution unit 101 executes payment based on information such as the credit card number indicated in the payment method information. It is assumed that information required for payment, such as the payment amount, is also included in the payment request.

Note that the processing performed by the payment execution unit 101 is not limited to the above example. In the case of payment types such as a code displayed on the store terminal 40 read by the user terminal 30, a code posted in the store read by the user terminal 30, a type that is completed by operating the user terminal 30 alone, a type that uses an IC chip in the user terminal 30, or any other type of payment, the payment execution unit 101 can acquire the information necessary for payment and execute the payment by communicating with at least one of the user terminal 30 and the store terminal 40. Once the payment execution unit 101 executes the payment, it updates the user's payment history information to indicate the details of the executed payment.

[Payment information acquisition section]
When a user using a payment service makes a payment using the user terminal 30, the payment information acquisition unit 102 acquires payment information related to the payment. When a user makes a payment using the user terminal 30, this means that the user performs an operation for payment from the user terminal 30. For example, when a user performs an operation for launching a payment app, an operation for displaying the code C10, an operation for having the store terminal 40 read the code C10, or other operation, this corresponds to the user performing a payment using the user terminal 30. Information processing for performing a payment is performed by the payment execution unit 101.

In this embodiment, the payment information acquisition unit 102 acquires payment information when a user makes a payment using the payment app on the user terminal 30. The payment information may be any information related to the content of the payment. For example, the payment information may be all or part of the information included in a payment request received by the payment server 10 from at least one of the user terminal 30 and the store terminal 40. The payment information may not be information included in the payment request, but may be information indicating the result of the payment. In other words, the payment information may be information indicating whether or not the payment has been made.

In this embodiment, the payment information acquisition unit 102 acquires payment information indicating the payment amount in a payment. For example, the payment information indicating the payment amount is included in the payment request. The payment information acquisition unit 102 acquires the payment information included in the payment request. After a payment is made, the payment amount is indicated in the payment history information, so the payment information acquisition unit 102 may acquire the payment information by acquiring information indicating the payment amount from the payment history information. Note that the payment information may indicate content other than the payment amount. Other examples of payment information will be described in the modified examples described below.

[App information acquisition section]
The app information acquisition unit 103 acquires app information I20 related to an app for a related service related to payment. In this embodiment, the app information acquisition unit 103 acquires app information I20 related to a mini app within a payment app. That is, although the example shows a case where the related service app is a mini app, the related service app may also be a normal app that is not a mini app. A normal app is an app that can be launched from a location other than the payment app, which is a super app. For example, an app whose icon is displayed on the home screen of the OS of the user terminal 30 corresponds to a normal app. A related service app is an app distributed by a business operator that provides a related service to a user.

App information I20 may refer to data related to the app, but in this embodiment it refers to objects (e.g., images, text, etc.) that are visually displayed on the payment completion screen SC2. The actual data for displaying app information I20 is assumed to be pre-stored in the data storage unit 100. The app information acquisition unit 103 acquires the app information I20 by acquiring the actual data. The actual data for displaying app information I20 may not be pre-stored in the data storage unit 100, but may be dynamically generated on the spot. In this case, the data that forms the basis of app information I20 is assumed to be stored in the data storage unit 100. The app information acquisition unit 103 may generate app information I20 based on the original data.

In this embodiment, the service provided by the card company that issued the credit card set by the user as the payment source corresponds to the related service, so the app information acquisition unit 103 acquires app information I20 for the installment payment app provided by the card company. For example, the app information acquisition unit 103 acquires app information I20 based on the payment amount indicated in the payment information. The app information acquisition unit 103 determines whether the payment amount indicated by the payment information is equal to or greater than a threshold. The threshold is an amount that serves as the criterion for determining whether or not to display app information I20. The threshold may be common to all users, or may be set for each user. For example, a threshold may be set for each demographic information, such as the user's gender or age group. The threshold is assumed to be stored in the data storage unit 100.

For example, if the app information acquisition unit 103 determines that the payment amount indicated by the payment information is equal to or greater than a threshold, it acquires app information I20 of the installment payment app. If the app information acquisition unit 103 determines that the payment amount indicated by the payment information is less than a threshold, it does not acquire app information I20 of the installment payment app. In the example of Figure 2, if it determines that the payment amount indicated by the payment information is less than the threshold, the app information acquisition unit 103 acquires other information I21, such as an advertisement, to be displayed instead of app information I20. It is assumed that the data for other information I21 is also stored in the data storage unit 100.

Note that the app information acquisition unit 103 may acquire app information I20 of an app other than the installment payment app if it determines that the payment amount indicated by the payment information is less than a threshold. That is, if it determines that the payment amount indicated by the payment information is equal to or greater than a threshold, the app information acquisition unit 103 may acquire app information I20 of a first app (in this embodiment, the installment payment app), and if it determines that the payment amount indicated by the payment information is less than the threshold, it may acquire app information I20 of a second app different from the first app (in this embodiment, an app other than the installment payment app).

Apps other than the installment payment app are likely to be of interest to users who have made small payments. For example, the other apps may be a points management app that allows users to manage their own points, an advertising app that allows users to earn points by viewing advertisements, an app that allows users to photograph and upload receipts, or a coupon app that allows users to earn coupons. These other apps may be mini-apps. The actual data for displaying the app information I20 of these other apps may be pre-stored in the data storage unit 100.

[Proposal Department]
The suggestion unit 104 suggests the app information I20 to the user on the user terminal 30. In the present embodiment, the suggestion unit 104 suggests the app information I20 to the user in a payment app on the user terminal 30. Proposing the app information I20 to the user means transmitting data for displaying the app information I20 to the user terminal 30 or another computer. In the present embodiment, the suggestion unit 104 suggests the app information I20 to the user on a payment completion screen SC2 that is displayed on the user terminal 30 when the payment is completed. The payment completion screen SC2 is a screen indicating that the payment has been completed. For example, the payment completion screen SC2 displays a message indicating that the payment has been completed, information about the payment location, the payment date and time, the payment amount, the payment target, or a combination thereof. In the present embodiment, an example is given in which the suggestion unit 104 displays the payment completion screen SC2 itself; however, the payment completion screen SC2 may be displayed by a function other than the suggestion unit 104. Regardless of the form in which the app information I20 is proposed, the proposal unit 104 may propose the app information I20 to the user on the payment completion screen SC2 by displaying the app information I20 as a pop-up on the payment completion screen SC2 or as a new screen superimposed on the payment completion screen SC2.

For example, when payment is completed and the app information acquisition unit 103 acquires app information I20, the suggestion unit 104 generates display data for a payment completion screen SC2 that includes the app information I20. The display data is data for displaying a screen on the user terminal 30. When a browser is used, the display data is HTML data. When a dedicated app such as a payment app is used, the display data is data (e.g., HTML data or image data) used to display a screen in the app. The suggestion unit 104 suggests app information I20 to the user by sending display data for the payment completion screen SC2 that includes the app information I20 to the user terminal 30. In this embodiment, the display data includes payment information. The payment server 10 may send the payment information to the user terminal 30 separately from the display data.

In this embodiment, the suggestion unit 104 determines whether the payment satisfies a predetermined condition, and suggests app information I20 to the user based on the result of this determination. The predetermined condition is a condition that serves as a criterion for whether the suggestion unit 104 will suggest app information I20. Data indicating the predetermined condition is stored in the data storage unit 100. In this embodiment, as described below, an example is given in which the predetermined condition is the payment amount, but the predetermined condition may be another condition. For example, the predetermined condition may be a condition that can be determined based on payment information.

For example, the suggestion unit 104 determines whether a predetermined condition is met based on the payment information. The suggestion unit 104 may determine whether the payment store is a predetermined store (for example, a store that handles high-priced items) as a predetermined condition other than the payment amount, which will be described later. The suggestion unit 104 may determine whether the payment timing is a predetermined timing (for example, before payday) as a predetermined condition. The suggestion unit 104 may determine whether the payment object is a predetermined object (for example, a high-priced item such as a home appliance). In these cases, the suggestion unit 104 may make a determination by combining multiple conditions from among the payment amount, payment store, payment timing, and payment object.

For example, the suggestion unit 104 may determine whether the payment amount is equal to or greater than a threshold, thereby determining whether the payment satisfies a predetermined condition. When the payment amount indicated by the payment information is equal to or greater than a threshold, the suggestion unit 104 suggests app information I20 indicating an installment payment app to the user. When the payment amount indicated by the payment information is less than the threshold, the suggestion unit 104 does not suggest app information I20 indicating an installment payment app to the user. In the example of FIG. 2 , when the payment amount indicated by the payment information is less than the threshold, the suggestion unit 104 suggests other information I21, such as an advertisement for another service, to the user. When the payment amount indicated by the payment information is less than the threshold, the suggestion unit 104 may not make any particular suggestion. For example, the suggestion unit 104 may suggest app information I20 of a first app (in this embodiment, an installment payment app) to the user when the payment amount indicated by the payment information is equal to or greater than a threshold, and may suggest app information I20 of a second app (in this embodiment, an app other than the installment payment app) to the user when the payment amount indicated by the payment information is less than the threshold.

For example, the suggestion unit 104 may suggest app information I20 based on whether the payment amount is equal to or greater than a threshold corresponding to the user's usage history of related services. The threshold may be an amount determined by the card company from past installment payment history (history of traditional installment payment methods). For example, if the user has made installment payments in the past, the threshold may be determined based on the amount of installment payments made by the user. This threshold may be the average amount of installment payments made by the user, the payment amount for which the user has made installment payments most frequently, or some other value.

Furthermore, when app information I20 for an installment payment app is proposed to a user, the card company may propose app information I20 for the installment payment app to users with a history of past installment payments. This is because users who have never used installment payments before are less likely to use an installment payment app. Based on the card company's history information, the relevant user and conditions (amount, etc.) may be extracted and linked to the payment service provider. The payment service provider may send payment data to the card when a payment that meets the conditions is made. Two-way data linking between the payment service provider and the card company can further deepen the link between the services.

Note that the method of proposing app information I20 is not limited to the above example. The suggestion unit 104 may suggest app information I20 to the user by sending data for displaying app information I20 to the user terminal 30 or another computer. For example, the suggestion unit 104 may suggest app information I20 to the user by displaying app information I20 on a screen other than the payment completion screen SC2 among the screens displayed in the payment app. The suggestion unit 104 may also suggest app information I20 to the user using means other than the payment app. The other means may be email, SMS, push notification, banner notification, or other means.

[3-2. Functions realized by related servers]
For example, the related server 20 includes a data storage unit 200 and a process execution unit 201. The data storage unit 200 is realized by the storage unit 22. The process execution unit 201 is realized by the control unit 21.

[Data storage unit]
The data storage unit 200 stores data necessary for the related services. For example, the data storage unit 200 stores a database that stores various information related to users who use the related services. In this embodiment, the related services correspond to services provided by the card company that issued the credit card, so the database stores various information related to the credit card. For example, the database stores the credit card number, expiration date, name of the cardholder, credit card usage history, payment method such as lump-sum payment or installment payment, and other information. The data storage unit 200 only needs to store data according to the related services.

[Processing execution unit]
The process execution unit 201 executes related service processing for providing related services to the user based on the data stored in the data storage unit 200. In this embodiment, the related services correspond to services provided by the card company that issued the credit card. Therefore, the process execution unit 201 executes related service processing for providing the user with various services, including a service for viewing the credit card usage history and a service for changing the payment method, such as lump-sum payment, installment payment, bonus payment, or revolving payment. In the example of FIG. 2 , the process execution unit 201 executes the related service processing by displaying the application screen SC3 on the user terminal 30 and accepting an installment payment application from the user. The process for accepting an installment payment application may be a known process.

The following describes the flow of conventional installment payments compared with the flow of installment payments in this embodiment. For example, in the conventional installment payment flow, when a payment is made with a credit card set as the payment source, the payment information for the credit card installment payment is reflected in the payment server 10, the related server 20 (the card company's server), and the cart company's website or app, in that order, before the user can apply for installment payments. As a result, the user cannot immediately apply for installment payments at the time of payment or immediately after payment. For example, when a user uses a credit card at a store, they can request installment payments from the store. However, in payments such as those using code C10 in this embodiment, the user cannot request installment payments from the store. This results in low user convenience in terms of installment payments. Furthermore, the rate of user use of installment payment services also decreases.

For example, in a conventional installment payment process, when a user makes a payment, the related server 20 obtains payment information directly or indirectly from the payment destination. The payment destination is a member of a payment service. When the related server 20 obtains payment information directly from the payment destination, it means that the related server 20 obtains payment information from the payment destination without going through another device. When the related server 20 obtains payment information indirectly from the payment destination, it means that the related server 20 obtains payment information from the payment destination via another device. In this embodiment, the payment destination corresponds to a store that has a store terminal 40. The related server 20 obtains payment information from the store terminal 40 or another computer (e.g., a server computer of the operating company that operates the store, or the payment server 10). The processing execution unit 201 executes related service processing based on the payment information. For example, if the related service is processing for installment payments, the processing execution unit 201 executes related service processing by accepting an application for installment payments for the payment indicated by the payment information obtained from the store terminal 40 or another computer.

In this embodiment, the period from when a payment is made until the payment recipient directly or indirectly sends payment information to the related server 20 is of a certain length. For example, this period may be two to three days, or it may be longer or shorter. This may also be the case in other cases besides when a user makes a payment using a user terminal 30. For example, even when a user makes a payment using a credit card, which is a so-called flat card, the period from when the payment is made until the store terminal 40 or another computer sends the payment information is of a certain length. This may also be the case for other payment methods other than credit cards (for example, electronic money or points).

For example, if the above-mentioned period exists, even if a user makes a payment, the user's payment is generally not reflected in the related service immediately. For this reason, even if the user makes a payment using a payment method such as a credit card, the user cannot log in to the related service and apply for installment payments immediately after making the payment. The user can apply for installment payments only after the payment recipient directly or indirectly sends payment information to the related server 20. The user generally needs to wait for the payment recipient to send payment information directly or indirectly to the related server 20. Furthermore, it may take time for the payment to be reflected on the payment service's website. Therefore, in this embodiment, user convenience is improved as follows.

The flow of installment payments in this embodiment will now be explained. With installment payments in this embodiment, payment information is linked to the related server 20 or related app immediately after payment, allowing the user to apply for installment payments directly. For example, if the user selects an installment payment app after it is suggested on the payment completion screen SC2, payment information is sent to the related server 20 or related app. This allows the user to apply for installment payments without waiting for payment information to be sent directly or indirectly from the payment destination to the related server 20.

Furthermore, the payment completion screen SC2 may not only suggest an installment payment app, but also allow the user to input the number of installments, etc. In this case, the input information, such as the number of installments, entered by the user may be sent to the related server 20 or the related app along with the payment information. In this case, compared to the method described in the previous paragraph, the user can complete the installment payment application without having to switch screens to the related app, etc., which is more convenient for the user. For example, the payment completion screen SC2 may not only suggest app information I20, but also allow the user to input input information. The transmission unit 305 transmits the payment information and the input information entered by the user to the related service. The transmission unit 305 transmits the payment information and the input information entered by the user to the related service. The input information is information that is referenced along with the payment information in related service processing. In the above example, the input information indicates the number of installments. For example, the input information may be other information, such as a bonus payment. The input information may also be information indicating that the installment payment application will be completed on the spot. If the related app is other than an installment payment app, the input information may be information corresponding to the other related app.

In this embodiment, the payment information is sent from the payment app to the related app by the transmission unit 305 described below, so the user's payment is reflected in the related service without the user having to wait the above-mentioned period. For example, the user can apply for installment payments immediately after making a payment. The related service processing executed by the processing execution unit may be the same whether the payment destination sends payment information directly or indirectly to the related server 20 or whether the payment information is sent by the transmission unit 305 described below. In other words, the related service processing after the related server 20 acquires the payment information may be the same as before.

[3-3. Functions implemented on user terminals]
For example, the user terminal 30 includes a data storage unit 300, an operation reception unit 301, a display control unit 302, a selection determination unit 303, a payment information acquisition unit 304, a transmission unit 305, and a process execution unit 306. The data storage unit 300 is realized by the memory unit 32. The operation reception unit 301, the display control unit 302, the selection determination unit 303, the payment information acquisition unit 304, the transmission unit 305, and the process execution unit 306 are realized by the control unit 31.

[Data storage unit]
The data storage unit 300 stores data necessary for the user to use a payment service. For example, the data storage unit 300 stores a payment app and related apps. When the user uses a payment service from a browser rather than the payment app, the data storage unit 300 stores the browser. The data storage unit 300 also stores data necessary for the user to use related services.

[Operation reception section]
The operation acceptance unit 301 accepts various operations from the user. For example, the operation acceptance unit 301 accepts operations on the payment app. The operation acceptance unit 301 transmits data indicating the content of the user's operation to the payment server 10. The operation acceptance unit 301 may also accept operations on related apps. The operation acceptance unit 301 may transmit data indicating the content of the user's operation to the related server 20.

[Display control unit]
The display control unit 302 displays various screens on the display unit 35. For example, the display control unit 302 displays a top screen SC1, a payment completion screen SC2, and an application screen SC3 on the display unit 35. The display control unit 302 communicates with the payment server 10, the related server 20, or another computer, receives data necessary to display these screens, and displays these screens on the display unit 35.

[Selection determination unit]
The selection determination unit 303 determines whether the user has selected the app information I20 on the user terminal 30. The selection determination unit 303 determines whether the user has selected the app information I20 based on an operation received by the operation reception unit 301. In the example of FIG. 2 , when the user performs an operation using the touch panel of the operation unit 34, the selection determination unit 303 determines whether the app information I20 has been selected based on a contact position detected by the touch panel. The selection determination unit 303 may also determine whether the app information I20 has been selected based on a detection signal from an input device other than the touch panel. In this embodiment, the user's selection of the app information I20 serves as a condition (trigger) for transmitting payment information to the associated app.

[Payment information acquisition section]
When a user using a payment service makes a payment using the user terminal 30, the payment information acquisition unit 304 acquires payment information related to the payment. In this embodiment, a payment app is used for the payment, so when a user makes a payment using the payment app of the user terminal 30, the payment information acquisition unit 304 acquires payment information related to the payment. The user may make a payment using a browser of the user terminal 30 instead of a payment app. In this case, the payment information acquisition unit 304 acquires payment information related to the payment made from the browser. Furthermore, the user may make a payment using an IC chip of the user terminal 30. In this case, the payment information acquisition unit 304 acquires payment information related to the payment made from the IC chip. The payment information may be written to the data storage unit 300 or the IC chip after the payment. The payment information acquisition unit 304 may acquire the payment information written in the data storage unit 300 or the IC chip.

In this embodiment, the display data of the payment completion screen SC2 includes payment information. Furthermore, the display data of the payment completion screen SC2 also includes data for displaying app information I20. In order to display the payment completion screen SC2, the user terminal 30 receives the display data of the payment completion screen SC2 from the payment server 10 and records it in the data storage unit 300. Therefore, the data storage unit 300 stores the payment information included in the display data. The payment information acquisition unit 304 acquires the payment information from the data storage unit 300. The payment information may be transmitted from the payment server 10 to the user terminal 30 separately from the display data of the payment completion screen SC2. The payment information acquisition unit 304 may acquire the payment information directly from the payment server 10. The payment information acquisition unit 304 can acquire the payment information at any time.

[Transmitter]
The transmitting unit 305 transmits payment information to an associated service related to the payment service. Transmitting payment information to an associated service means transmitting the payment information to an associated app via internal communication (e.g., inter-process communication) of the user terminal 30, or transmitting the payment information to an associated server 20 of the associated service. In other words, transmitting payment information to an associated service means recording the payment information in a storage area accessible by the associated app or the associated server 20. In this embodiment, the transmitting unit 305 transmits the payment information to the associated app. The associated app acquires the payment information transmitted by the transmitting unit 305.

In this embodiment, because the user makes a payment using the payment app and the associated app is installed on the user terminal 30, the transmission unit 305 transmits payment information for the payment made by the user using the payment app to the associated app. That is, the transmission unit 305 transmits the payment information to the associated app of the user terminal 30. For example, the transmission unit 305 transmits the payment information from the payment app to the associated app through internal communication within the user terminal 30 (e.g., inter-process communication between the payment app and the associated app). The program code indicating the process of transmitting the payment information is included in the payment app, but may also be included in an application other than the payment app. The transmission unit 305 may also transmit the payment information to the associated server 20. This point will be explained in the modified example described below.

In this embodiment, an associated app, such as an installment payment app, is proposed to the user, and the transmission unit 305 transmits payment information to the associated app for which app information I20 has been proposed on the user terminal 30. For example, the transmission unit 305 transmits payment information to the associated app when it is determined that the user has selected app information I20. That is, the transmission unit 305 transmits payment information to the associated app on the condition (trigger) that the selection determination unit 303 has determined that the user has selected app information I20. Note that the transmission unit 305 may transmit payment information to the associated app on the condition that app information I20 has been proposed, even if the user has not selected app information I20. As another example, the transmission unit 305 may transmit payment information to the associated app on the condition that the payment information acquisition unit 304 has acquired payment information.

In this embodiment, the transmission unit 305 does not transmit payment information to associated apps for which the app information I20 was not proposed on the user terminal 30. For example, if it is not determined that the user has selected the app information I20, the transmission unit 305 does not transmit payment information to the associated apps. Note that the transmission unit 305 may also transmit payment information to associated apps for which the app information I20 was not proposed on the user terminal 30. In this case, the transmission unit 305 may transmit payment information to all associated apps, or may transmit payment information to some of the associated apps. The transmission unit 305 may also transmit payment information to associated apps based on an operation other than the selection of the app information I20.

In this embodiment, if the user does not select app information I20, the payment information is reflected in the related service when it is sent directly or indirectly from the payment destination to the related app. This is as explained in the function of the processing execution unit 201 of the related server 20. The sending unit 305 sends payment information to the related app when it is determined that the user has selected app information I20 before the payment information is sent directly or indirectly from the payment destination to the related app. In other words, the sending unit 305 can send payment information to the related app without waiting for the period until the payment information is sent directly or indirectly from the payment destination to the related app.

In this embodiment, the condition (trigger) for transmitting payment information is the user's selection of app information I20; however, the condition may also be the user's operation other than selecting app information I20. For example, the other operation may be the user's operation to instruct the transmission of payment information, the user's manual launch of an associated app by an operation other than selecting app information I20, a specific operation on the user terminal 30 (e.g., shaking the user terminal 30), or some other operation. The transmission unit 305 may determine whether a predetermined operation that is a condition for transmitting payment information has been performed, and may transmit payment information to the associated app if it is determined that the predetermined operation has been performed. As another example, the transmission unit 305 may transmit payment information after the aforementioned input information (e.g., information indicating the input of the number of installments, etc.) has been input. In this case, the input of installments corresponds to the condition (trigger) for transmitting payment information.

For example, the specified operation may be the selection of a related app from the app list L11. The transmission unit 305 may determine whether an installment payment app, which is an example of a related app, has been selected from the app list L11, and may transmit payment information to the installment payment app if it is determined that the installment payment app has been selected from the app list L11. If the app information I20 displayed on the payment completion screen SC2 is information for displaying the app list L11 or another app list, the transmission unit 305 may transmit payment information to the installment payment app if the user selects the app information I20 and selects the installment payment app from the displayed app list L11 or another app list.

For another example, the predetermined operation may be an operation performed from a related app. Taking an installment payment app as an example, the predetermined operation may be an operation performed on the installment payment app. When a user performs an operation on the installment payment app to instruct the transmission of payment information, the transmission unit 305 may transmit payment information to the installment payment app. For example, when an image or text such as "Get latest payment information from payment app" is displayed on the installment payment app and the user selects the image or text, the transmission unit 305 may transmit payment information to the installment payment app.

The sending unit 305 may send payment information to the associated app based on conditions other than the user performing a predetermined operation. For example, the sending unit 305 may send payment information to the associated app when the payment completion screen SC2 is closed. The sending unit 305 may also send payment information to the associated app when a predetermined time (e.g., several seconds to several minutes) has passed since the completion of the payment. In this case, the elapsed time is shorter than the period until the payment destination directly or indirectly sends payment information to the associated server 20.

For another example, the transmission unit 305 may determine whether there is payment information that is not stored in the database stored in the data storage unit 200 of the associated server 20, and if such payment information exists, transmit the payment information to the associated app. This determination may be made by the user terminal 30 and the associated server 20 cooperating with each other. For example, the user terminal 30 may obtain from the associated server 20 the user's payment information stored in the associated server's 20 database, and determine whether the payment information obtained by the payment information acquisition unit 304 is stored in the database. The user terminal 30 may transmit the payment information obtained by the payment information acquisition unit 304 to the associated server 20 and request the associated server 20 to make a determination.

[Processing execution unit]
The processing execution unit 306 executes related service processing for the related service based on the related app and the payment information transmitted to the related app. The related service processing is processing for the user to use the related service. In this embodiment, processing for installment payments will be described as an example of the related service processing. An installment payment application is made by the user terminal 30 communicating with the related server 20, so the related service processing includes processing for this communication. For example, the related service processing may be processing in which the user terminal 30 transmits payment information received by the related app to the related server 20. The related service processing may also be other processing, such as processing for displaying the payment information on the related app. In this embodiment, the user terminal 30 executes the related service processing in cooperation with the related server 20, so the related service processing includes processing on the user terminal 30 side and processing on the related server 20 side. The processing on the related server 20 side is the same as that described as the processing of the processing execution unit 201 of the related server 20. The processing on the user terminal 30 side will be described below.

In this embodiment, the related app is an app that accepts payment-related adjustments, so the process execution unit 306 executes adjustment processing related to the adjustment as related service processing based on the related app and the payment information sent to the related app. Changing to installment payment is an example of an adjustment. Adjustments are not limited to installment payment. For example, changing to deferred payment, changing to bonus payment or revolving payment, changing the payment method, applying a coupon after the fact, or changing the point allocation amount may also correspond to an adjustment. Any subsequent change made by the user to the details of a payment may correspond to an adjustment. In this embodiment, installment payment is described as an example of an adjustment. The term "installment payment" can be replaced with the other adjustments listed above.

For example, the process execution unit 306 executes the related app on the user terminal 30 and executes the reconciliation process by transmitting payment information acquired by the related app to the related server 20. The reconciliation process may include processing for accepting the designation of the number of installments, processing for calculating the amount of each payment, processing for storing the details of the installments in the database of the related server 20, or other processing. Since the reconciliation process is an example of related service processing, the process execution unit 306 executes the related service processing based on the related app on the user terminal 30 and the payment information transmitted to the related app on the user terminal 30. The related server 20 acquires the payment information transmitted by the related app. This allows the related server 20 to execute the installment payment process without waiting for payment information to be transmitted directly or indirectly from the payment destination. The process execution unit 306 may execute the reconciliation process based on the related app by displaying the payment information acquired by the related app on the related app.

[3-4. Functions realized by store terminals]
For example, the store terminal 40 includes a data storage unit 400 and a payment execution unit 401. The data storage unit 400 is realized by the storage unit 42. The payment execution unit 401 is realized by the control unit 41.

[Data storage unit]
The data storage unit 400 stores data necessary for providing payment services to users. For example, the data storage unit 400 stores a database that stores various information such as the prices of products or services handled by a store. The data storage unit 400 also stores information on products or services that users are the subject of payment for. The data storage unit 400 may also store information on the location where the store terminal 40 is located.

[Payment Execution Department]
The payment execution unit 401 provides a payment service to the user. For example, when the store terminal 40 reads the code C10 with the reading unit 46, the payment execution unit 401 acquires a code ID from the code C10. The payment execution unit 401 acquires the payment amount based on the results of reading the barcode of the product, etc. The payment execution unit 401 transmits a payment request to the payment server 10, including information necessary for payment, such as the code ID, payment amount, and store location. The payment request may be any request used in a known payment service. The payment execution unit 401 acquires the execution result of the payment from the payment server 10 and completes the payment at the store. This series of processes may also be any process used in a known payment service.

4. Processing Executed by Payment System 1
5 and 6 are diagrams showing an example of processing executed in payment system 1. Control units 11, 21, 31, and 41 execute programs stored in storage units 12, 22, 32, and 42, respectively, to execute the processing of FIGS.

As shown in FIG. 5, when the payment app is launched on the user terminal 30, the payment server 10 executes processing with the user terminal 30 to display the top screen SC1 (S1). In S1, the payment server 10 has the user log in to the payment service, generate a code ID, and send display data for the top screen SC1 to the user terminal 30. The user then has the store terminal 40 read the code C10. When the store terminal 40 reads the code C10 with the reading unit 46 (S2), it extracts the code ID from the code C10 and sends a payment request to the payment server 10 (S3). When the payment server 10 receives the payment request (S4), it executes the payment based on the payment request (S5).

The payment server 10 references the payment request received in S4 and acquires payment information indicating the payment amount of the payment executed in S5 (S6). The payment server 10 determines whether the payment amount indicated by the payment information acquired in S6 is equal to or greater than a threshold (S7). If it is determined in S7 that the payment amount is equal to or greater than the threshold (S7: Y), the process moves to FIG. 6, where the payment server 10 acquires app information I20 of the installment payment app (S8). The payment server 10 executes processing with the user terminal 30 to propose the app information I20 of the installment payment app on a payment completion screen SC2 (S9). In S9, the payment server 10 generates display data for the payment completion screen SC2 including the app information I20 of the installment payment app and transmits it to the user terminal 30. The user terminal 30 displays the payment completion screen SC2, as shown in the upper right corner of FIG. 2, on the display unit 35.

The user terminal 30 determines whether the user has selected app information I20 (S10). If it is determined in S10 that the user has not selected app information I20 (S10: N), this process ends. In this case, payment information is not sent to the related app. If it is determined in S10 that the user has selected app information I20 (S10: Y), the user terminal 30 acquires the payment information recorded in a memory area accessible to the payment app (S11). In the process of S9, the payment information is recorded in a memory area accessible to the payment app within the memory area of the memory unit 32 of the user terminal 30.

The user terminal 30 transmits the payment information acquired in S11 to the associated app stored in the user terminal 30 (S12). Based on the payment information transmitted in S12, the user terminal 30 executes associated service processing with the associated server 20 to display the app screen SC3 (S13), and this processing ends. In S13, the user terminal 30 launches the installment payment app and transmits the payment information to the associated server 20. The associated server 20 generates display data for the app screen SC3 and transmits it to the user terminal 30. Thereafter, the processing for the installment payment executed in S5 is executed.

If it is determined in S7 that the payment amount is less than the threshold value (S7: N), the payment server 10 executes processing with the user terminal 30 to display a payment completion screen SC2 that does not include app information I20 (S14), and this processing ends. In S14, the payment server 10 generates display data for the payment completion screen SC2 that includes other information I21, such as advertisements, and transmits it to the user terminal 30. The user terminal 30 displays the payment completion screen SC2, as shown in the lower left of Figure 2, on the display unit 35 and executes processing in accordance with the user's operation.

5. Summary of the embodiment
In this embodiment, the payment system 1 acquires payment information when a user using a payment service executes a payment using a user terminal 30. The payment system 1 transmits the payment information to a related service related to the payment service. This allows the related service to acquire the payment information of the payment executed in the payment service, and the payment system 1 can enhance cooperation between the payment service and the related service. For example, the payment system 1 can transmit the payment information to a related app without going through another computer such as a payment destination, and therefore the payment information can be quickly reflected in the related service. For example, the user can immediately execute various processes, such as installment payments, related to the payment executed by the user in the related service, and the payment system 1 can improve user convenience.

The payment system 1 also acquires app information I20 based on the payment information. The payment system 1 proposes app information I20 to the user via the user terminal 30. The payment system 1 transmits payment information to the related app for which app information I20 has been proposed via the user terminal 30. The payment system 1 proposes app information I20 to the user via the user terminal 30. This allows the payment system 1 to propose app information I20 of related services related to the payment performed by the user to the user. For example, the payment system 1 can encourage users to use apps. The payment system 1 eliminates the need for users to search for and launch the desired app on the user terminal 30, thereby improving user convenience. When a user selects app information I20 to use the related app, the payment system 1 can cause the related app to quickly acquire payment information.

The payment system 1 also determines whether the payment satisfies predetermined conditions and suggests app information I20 to the user based on the results of this determination. This allows the payment system 1 to suggest app information I20 to users for whom the suggestion of app information I20 is valid. The payment system 1 can make users aware of the existence of the app indicated by app information I20 and motivate them to use the app. For example, the payment system 1 can suggest information other than app information I20 to users for whom the suggestion of app information I20 is valid, thereby making effective use of the display space on the screen.

The payment system 1 also determines whether the payment amount is equal to or greater than a threshold, thereby determining whether the payment satisfies predetermined conditions. When the validity of the proposal for app information I20 depends on the payment amount, the payment system 1 can propose app information I20 to the user based on the payment amount, thereby enhancing the appealing effect. When making proposals based on other factors besides the amount, such as the payment store, payment timing, or payment object, the payment system 1 can propose app information I20 based on these factors, thereby enhancing the appealing effect.

The payment system 1 also proposes app information I20 based on whether the payment amount is equal to or exceeds a threshold value corresponding to the user's usage history of related services. This allows the payment system 1 to further deepen the collaboration between the payment service and related services by linking data between them in both directions. For example, the related server 20 extracts relevant users and conditions (such as usage amount) based on the usage history of the related services, and links this to the payment server 10. When a payment that meets the conditions is made in the payment service, the payment server 10 transmits the payment data of the payment to the related server 20, thereby enabling two-way data collaboration.

Furthermore, the payment system 1 proposes app information I20 to the user on a payment completion screen SC2 that is displayed on the user terminal 30 when payment is completed. This allows the payment system 1 to more effectively propose app information I20 to the user by proposing app information I20 on the payment completion screen SC2, which is likely to be noticed by the user. When the user selects app information I20 and uses a related app immediately after completing payment, the payment system 1 can allow the related app to quickly obtain payment information.

In addition, the payment system 1 not only proposes app information I20 on the payment completion screen SC2, but also allows the user to input input information. The payment system 1 transmits the payment information and input information to the related service. For example, compared to when an installment payment app is proposed on the payment completion screen SC2 and payment information is transmitted when the user selects the installment payment app, the user can apply for installment payments directly without transitioning to another screen, such as a related app, and the payment system 1 can therefore improve user convenience.

The payment system 1 also determines whether the user has selected app information I20 on the user terminal 30. If it is determined that the user has selected app information I20, the payment system 1 sends payment information to the associated app. This allows the payment system 1 to send payment information to the associated app when the associated app requires payment information. For example, if the user does not select app information I20, the associated app does not require payment information, so it is possible to prevent payment information from being sent to the associated app even in such cases. This allows the payment system 1 to prevent the user terminal 30 from performing unnecessary processing.

In addition, in payment system 1, if it is determined that the user has selected app information I20 before payment information is sent directly or indirectly from the payment destination to the associated app, the sending unit 305 sends payment information to the associated app. This allows the user to use associated services such as installment payments without waiting for payment information to be sent directly or indirectly from the payment destination to the associated app, so payment system 1 can improve user convenience. For example, if the user waits for payment information to be sent directly or indirectly from the payment destination to the associated app, there is a possibility that the user will forget to apply for installment payments. However, since the user can apply for installment payments immediately after payment, payment system 1 can prevent the user from forgetting to apply for installment payments.

In addition, the payment system 1 executes an adjustment process as a related service process based on the related app and the payment information transmitted to the related app. This allows the user to make adjustments such as installment payments immediately after payment, thereby improving user convenience.

The payment system 1 also transmits payment information to the associated app of the user terminal 30. The payment system 1 executes the associated service process based on the associated app of the user terminal 30 and the payment information transmitted to the associated app of the user terminal 30. This allows the payment system 1 to have the associated app obtain the payment information through internal communication within the user terminal 30.

6. Modifications
The present disclosure is not limited to the above-described embodiments, and may be modified as appropriate without departing from the spirit of the present disclosure.

Figure 7 is a diagram showing an example of functions implemented in this modified example. For example, the user terminal 30 includes a necessity determination unit 307, an amount determination unit 308, and a payment method determination unit 309. Each of the necessity determination unit 307, amount determination unit 308, and payment method determination unit 309 is implemented by the control unit 31.

[6-1. Modification 1]
For example, the related app proposed in the app information I20 is not limited to an installment payment app. Other apps, such as an invoice app for paying bills such as utility bills, may also be proposed in the app information I20. In this case, payment information may not be required depending on the related app proposed to the user. For example, since the invoices to be paid by the invoice app are basically unrelated to the payments made by the user, the invoice app basically does not require payment information. Therefore, whether or not payment information needs to be sent may be determined based on the related app proposed to the user.

In variant 1, the payment server 10 selects from multiple related apps a related app for which the suggestion unit 104 proposes app information I20. The payment server 10 may select at least one related app based on a predetermined selection method. In variant 1, an example is given in which the payment server 10 selects one related app, but the payment server 10 may select multiple related apps. In variant 1, a method based on payment information is described as an example of a selection method. Note that the selection of the related app may be performed by the user terminal 30. In this case, it is assumed that data necessary for the payment server 10 to select the related app is stored in the user terminal 30. The process described as being performed by the payment server 10 may also be performed by the user terminal 30.

For example, it is assumed that proposal relationship data indicating the relationship between payment information and a related app that should be proposed to the user from among multiple related apps is stored in advance in the data storage unit 100. The proposal relationship data may be in any format, such as a table, a mathematical formula, part of program code, or a machine learning model. The payment server 10 selects the related app associated with the payment information. Note that the actual data of the app information I20 for each related app is also stored in the data storage unit 100.

In Variation 1, as in the embodiment, an example is given in which the payment information indicates a payment amount. The proposal relationship data indicates whether the payment amount is equal to or greater than a threshold, and the relationship between the payment amount and the related app that should be suggested to the user from among multiple related apps. For example, based on the proposal relationship data, the payment server 10 selects an installment payment app if the payment amount indicated by the payment information is equal to or greater than a threshold. Based on the proposal relationship data, the payment server 10 selects another related app, such as an invoice app, if the payment amount indicated by the payment information is less than the threshold.

In addition, even if the payment information indicates content other than the payment amount, the proposal relationship data indicates the relationship between that content and the related app that should be suggested to the user from among multiple related apps. The payment server 10 can select a related app that is associated with the other content indicated by the payment information based on the proposal relationship data. For example, the payment server 10 may select a related app that should be suggested to the user based on at least one of the payment location, payment time, and payment method indicated in the payment information. In this case, the proposal relationship data indicates the relationship between at least one of these and the related app that should be suggested to the user.

The app information acquisition unit of Variation 1 acquires app information I20 of the related app selected by the payment server 10. For example, if multiple related apps are selected by the payment server 10, the app information acquisition unit acquires app information I20 for each of the multiple related apps. The process by which the app information acquisition unit acquires app information I20 may be the same as in the embodiment. The suggestion unit of Variation 1 proposes to the user, via the user terminal 30, the app information I20 of the related app selected by the payment server 10. For example, if multiple related apps are selected by the payment server 10, the suggestion unit proposes app information I20 for each of the multiple related apps.

The payment system 1 of variant 1 includes a necessity determination unit 307. The necessity determination unit 307 of variant 1 determines whether it is necessary to transmit payment information to the related service of the related app selected by the payment server 10. Transmission necessity data indicating whether it is necessary to transmit payment information is stored in advance in the data storage unit 300. The transmission necessity data indicates at least one of related apps for which payment information needs to be transmitted and related apps for which payment information does not need to be transmitted. The transmission necessity data may indicate both of these.

For example, for an installment payment app, the transmission necessity data indicates that payment information needs to be sent. On the other hand, for an invoice app, the transmission necessity data indicates that payment information does not need to be sent. The transmission necessity data may also indicate whether payment information needs to be sent to other related apps. For example, the transmission necessity data may indicate that payment information needs to be sent to a points management app that manages points, or an asset management app that manages the user's assets. The transmission necessity data may indicate that payment information does not need to be sent to a coupon management app that manages coupons, or a travel booking app that books travel products.

For example, the necessity determination unit 307 determines whether it is necessary to transmit payment information to the related app selected by the payment server 10, based on the transmission necessity data. The user terminal 30 is assumed to have acquired information for identifying the related app selected by the payment server 10 (for example, the name of the related app or an ID that can uniquely identify the related app) from the payment server 10. This information may be included in the display data of the payment completion screen SC2, or may be separate data from the display data of the payment completion screen SC2.

In variant 1, if the necessity determination unit 307 determines that it is not necessary to transmit payment information, the transmission unit 305 does not transmit payment information to the related service of the related app selected by the payment server 10. If the necessity determination unit 307 determines that it is necessary to transmit payment information, the transmission unit 305 transmits payment information to the related service of the related app selected by the payment server 10. For example, if multiple related apps are selected by the payment server 10, the transmission unit 305 transmits payment information to the related app of the multiple related apps for which it is determined by the necessity determination unit 307 that it is necessary to transmit payment information. The processing after the payment information is transmitted may be the same as in the embodiment.

In the payment system 1 of variant 1, if it is determined that sending payment information is not necessary, the payment system 1 does not send payment information to the related service of the related app selected by the payment server 10, but if the necessity determination unit 307 determines that sending payment information is necessary, the payment system 1 sends payment information to the related service of the related app selected by the payment server 10. As a result, the payment system 1 does not send payment information to the related service of the related app that does not require payment information, and therefore does not execute unnecessary processing. Since the payment system 1 sends payment information to the related app that does require payment information, it is possible to improve the collaboration between the payment service and the related services.

[6-2. Modification 2]
For example, in the embodiment, a case has been described in which the related app is stored in the user terminal 30. The related app may be stored in a computer other than the user terminal 30. In Modification 2, an example is given in which the related app is stored in the related server 20. The related app indicates processing that the related server 20 should execute to provide the related service. For example, the related app may be an application corresponding to the API of the related server 20 (e.g., an application for acquiring payment information), an application executed based on information acquired by the API of the related server 20 (e.g., an application indicating installment payment processing executed based on payment information acquired by the API), or other applications. The data storage unit 200 in Modification 2 stores the related app.

The transmitting unit 305 in variant 2 transmits payment information to the associated server 20 of the associated service. For example, the transmitting unit 305 executes a payment app and transmits payment information to the associated app of the associated server 20. The transmitting unit 305 may transmit payment information directly to the associated app of the associated server 20, or may transmit payment information indirectly. For example, if the API of the associated server 20 corresponds to the associated app, the transmitting unit 305 transmits payment information directly to the associated app of the associated server 20. If the application executed based on information acquired by the API of the associated server 20 corresponds to the associated app, the transmitting unit 305 transmits payment information indirectly to the associated app of the associated server 20 via the API of the associated server 20.

For example, the processing execution unit 201 of the related server 20 executes the related service processing based on the payment information sent to the related server 20. The processing execution unit 201 of the related server 20 executes the related service processing based on the payment information sent to the related server 20. This embodiment differs from the embodiment in that the application stored in the related server 20 corresponds to the related app, but the method of executing the related service processing may be the same as the embodiment.

The payment system 1 of variant 2 transmits payment information to the related server 20 of the related service. The payment system 1 executes related service processing based on the payment information transmitted to the related server 20. This allows the payment system 1 to transmit payment information to the related server 20 by having the user terminal 30 communicate with the related server 20, thereby enhancing collaboration between the payment service and the related service.

[6-3. Modification 3]
For example, the related app may require payment information when a large payment is made. In the case of the installment payment app described in the embodiment, a user may apply for installment payments for a large payment. Therefore, the payment information may be transmitted when it is determined that the payment amount is equal to or greater than a predetermined amount. The payment system 1 of the third modification includes an amount determination unit 308. The amount determination unit 308 determines whether the payment amount is equal to or greater than a predetermined amount.

The predetermined amount may be the same as the amount used to display the installment payment app information I20 described in the embodiment, or it may be different from this amount. Data indicating the predetermined amount is stored in the data storage unit 300. In variant 3, the transmission unit 305 transmits payment information to the related service if it determines that the payment amount is equal to or greater than the predetermined amount. If it determines that the payment amount is less than the predetermined amount, the transmission unit 305 does not transmit payment information to the related service. The processing after the payment information has been transmitted may be the same as in the embodiment.

In variant 3, the payment system 1 determines whether the payment amount in a payment is equal to or greater than a predetermined amount. If it determines that the payment amount is equal to or greater than the predetermined amount, the payment system 1 transmits payment information to the related service. This allows the payment system 1 to provide payment information when a high-value payment is made, for which the related app is likely to require payment information. The payment system 1 can refrain from providing payment information when a low-value payment is made, for which the related app is likely not to require payment information.

[6-4. Modification 4]
For example, the payment information may be transmitted when it is determined that the payment method used for the payment is a predetermined payment method. In the example of FIG. 2, the payment method used for the payment is the payment method set as the payment source. The user can set any payment method from among multiple payment methods as the payment source. Information that can identify the payment method set as the payment source is stored in the user database DB. This information may be stored in the user terminal 30.

The payment system 1 of variant 4 includes a payment method determination unit 309. The payment method determination unit 309 determines whether the payment method used for payment is a predetermined payment method. A predetermined payment method is a payment method for which payment information needs to be transmitted. A predetermined payment method can also be said to be a payment method that satisfies the conditions for the transmission unit 305 to transmit payment information. For example, if an installment payment app corresponds to an associated app, then a credit card provided by a card company that provides the associated app corresponds to the predetermined payment method.

The predetermined payment method data indicating the predetermined payment method is stored in advance in the data storage unit 300. The payment method determination unit 309 determines whether the payment method used for payment is the predetermined payment method based on the predetermined payment method data. The predetermined payment method may be any payment method and is not limited to a credit card from the card company that provides the related app. For example, electronic money provided by a specific company or points provided by a specific company may correspond to the predetermined payment method. Alternatively, for example, the predetermined payment method may not be limited to a specific company, but may include credit cards in general, electronic money in general, or points in general.

In variant 4, the sending unit 305 sends payment information to the related service if it is determined that the payment method used in the payment is a specified payment method. If it is determined that the payment method is not a specified payment method, the sending unit 305 does not send payment information to the related service. The processing after the payment information is sent may be the same as in the embodiment. Note that the sending unit 305 may send payment information to the related app if it is determined that the specified payment method is included in the multiple payment methods used in the payment. In this case, it may send payment information only for payments made using the specified payment method.

In variant 4, the payment system 1 determines whether the payment method used in the payment is a specified payment method. If the payment method is determined to be a specified payment method, the payment system 1 transmits payment information to the related service. This allows the payment system 1 to provide payment information when the payment is made using a payment method for which the related service is likely to require payment information. The payment system 1 can refrain from providing payment information when the payment is made using a payment method for which the related service is likely not to require payment information.

[6-5. Other Modifications]
For example, the above modifications may be combined.

For example, while the embodiment illustrates an example in which a user uses a payment service through a payment app, the user may also use the payment service through the browser on the user terminal 30. In this case, the user may make the payment by having the store terminal 40 read the code C10 displayed on the browser, or may make the payment online rather than at a store without using the code C10. Online payments are completed solely by operating the user terminal 30. For example, the user may make payments for online e-commerce services, e-book services, travel booking services, communication services, or other services from the browser. When such an online payment is made, the payment system 1 may send payment information to the associated app.

For example, the computer that transmits the payment information to the associated app may be a computer other than the user terminal 30. For example, the payment server 10 may transmit the payment information to the associated app of the user terminal 30. In this case, the transmission unit 305 is realized by the payment server 10. The transmission unit 305 of the payment server 10 may transmit the payment information to the associated app of the associated server 20. In this way, the mode in which the payment server 10 transmits the payment information to the associated app is also included in the scope of the present disclosure.

For example, the payment system 1 may present app information I20 to the user, and when the user selects app information I20, the payment system 1 may display on the user terminal 30 details for using the related app (for example, for applying for installment payments) within the payment completion screen SC2, or on a screen overlaid on the payment completion screen SC2 or on a separate screen. Furthermore, the payment system 1 may accept input from the user. Up to this point, this is performed as processing on the payment service side. The payment system 1 may send payment information to the related service and execute related service processing. The related service processing may be executed as processing on the related service side. That is, processing such as accepting input for installment payments may be executed as processing on the related service side.

For example, functions described as being implemented by the payment server 10 may be implemented by the related server 20, the user terminal 30, the store terminal 40, or another computer. Processing described as being implemented by the payment server 10 may be shared among multiple computers. Functions described as being implemented by the user terminal 30 may be implemented by the payment server 10, the related server 20, the store terminal 40, or another computer. Processing described as being implemented by the user terminal 30 may be shared among multiple computers.

[7. Notes]
For example, the payment system can be configured as follows:
(1)
a payment information acquisition unit that acquires payment information related to a payment when a user who uses the payment service makes a payment using a user terminal;
a transmitting unit that transmits the payment information to a related service that is related to the payment service;
Payment systems, including:
(2)
The payment system includes:
an application information acquisition unit that acquires application information related to an application associated with the associated service;
a suggestion unit in the user terminal that proposes the application information to the user;
Further comprising:
the transmitting unit transmits the payment information to the related service of the related app for which the app information has been proposed on the user terminal.
A payment system as described in (1).
(3)
the suggestion unit determines whether the payment satisfies a predetermined condition, and suggests the app information to the user based on the result of the determination.
(2) A payment system according to the present invention.
(4)
the proposal unit determines whether the payment amount of the payment is equal to or greater than a threshold, thereby determining whether the payment satisfies the predetermined condition;
(3) A payment system according to the present invention.
(5)
the suggestion unit suggests the app information based on whether the payment amount is equal to or greater than the threshold value according to the user's usage history of the related service.
(4) A payment system according to the present invention.
(6)
the suggestion unit suggests the app information to the user on a payment completion screen displayed on the user terminal when the payment is completed.
A payment system according to any one of (2) to (5).
(7)
The payment completion screen not only allows the user to propose the app information but also allows the user to input input information,
The transmission unit transmits the payment information and the input information to the related service.
(6) A payment system according to the present invention.
(8)
The payment system further includes a selection determination unit that determines whether the user has selected the app information on the user terminal;
the transmitting unit transmits the payment information to the related service when it is determined that the user has selected the app information.
A payment system according to any one of (2) to (7).
(9)
If the user does not select the application information, when the payment information is sent directly or indirectly from the payment destination to the related application, the payment information is reflected in the related service,
the transmitting unit transmits the payment information to the related service when it is determined that the user has selected the application information before the payment information is transmitted from the payment destination to the related application.
(8) A payment system according to (8).
(10)
the application information acquisition unit acquires the application information of the related application selected from the plurality of related applications;
the suggestion unit suggests, to the user, the app information of the selected related app, at the user terminal;
the payment system further includes a necessity determination unit that determines whether or not it is necessary to transmit the payment information for the related service of the selected related app;
When the necessity determination unit determines that transmission of the payment information is unnecessary, the transmission unit does not transmit the payment information to the related service of the selected related application, and when the necessity determination unit determines that transmission of the payment information is necessary, the transmission unit transmits the payment information to the related service of the selected related application.
A payment system according to any one of (2) to (9).
(11)
The related service is a service that accepts adjustments regarding the payment.
A payment system according to any one of (1) to (10).
(12)
The payment system further includes an amount determination unit that determines whether a payment amount in the payment is equal to or greater than a predetermined amount,
the transmitting unit transmits the payment information to the related service when it is determined that the payment amount is equal to or greater than the predetermined amount.
A payment system according to any one of (1) to (11).
(13)
The payment system further includes a payment method determination unit that determines whether the payment method used for the payment is a predetermined payment method,
the transmitting unit transmits the payment information to the related service when it is determined that the payment method is the predetermined payment method.
A payment system according to any one of (1) to (12).

1 Payment system, 10 Payment server, 11, 21, 31, 41 Control unit, 12, 22, 32, 42 Memory unit, 13, 23, 33, 43 Communication unit, 20 Related server, 30 User terminal, 34, 44 Operation unit, 35, 45 Display unit, 36 Photography unit, 40 Store terminal, 46 Reading unit, 100 Data storage unit, 101 Payment execution unit, 102 Payment information acquisition unit, 103 Application information acquisition unit, 104 Proposal unit, 200 Data storage unit, 201 Processing execution unit, 300 Data storage unit, 301 Operation acceptance unit, 302 Display control unit, 303 Selection determination unit, 304 Payment information acquisition unit, 305 Transmission unit, 306 Processing execution unit, 307 Necessity determination unit, 308 Amount determination unit, 309 Payment method determination unit, 400 Data storage unit, 401 payment execution unit, N network, DB user database, C10 code, I20 application information, I21 other information, L11 application list, SC1 top screen, SC2 payment completion screen, SC3 application screen.

Claims (14)

a payment information acquisition unit that acquires payment information regarding a payment after a user who uses a payment service completes a payment using a user terminal;
an application information acquisition unit that acquires application information related to an application of a related service that is related to the payment service;
a suggestion unit that suggests the app information to the user on the user terminal based on whether or not a payment amount in the payment is equal to or greater than a threshold according to a usage history of the related service by the user;
a transmission unit that transmits the payment information to a server computer of the related service of the related app for which the app information is proposed on the user terminal or to the related app ;
Payment systems, including: a payment information acquisition unit that acquires payment information regarding a payment after a user who uses a payment service completes a payment using a user terminal;
an application information acquisition unit that acquires application information related to an application of a related service that is related to the payment service;
a proposal unit that proposes the app information to the user on a payment completion screen that is displayed on the user terminal when the payment is completed;
a transmission unit that transmits the payment information to a server computer of the related service of the related app for which the app information is proposed on the user terminal or to the related app;
Payment systems, including : The payment completion screen not only allows the user to propose the app information but also allows the user to input input information,
the transmitting unit transmits the payment information and the input information to the server computer or the related application of the related service.
The payment system according to claim 2 . a payment information acquisition unit that acquires payment information regarding a payment after a user who uses a payment service completes a payment using a user terminal;
an application information acquisition unit that acquires application information related to an application of a related service that is related to the payment service;
a suggestion unit in the user terminal that proposes the application information to the user;
a selection determination unit that determines whether the user has selected the application information on the user terminal;
a transmitting unit that, when it is determined that the user has selected the app information, transmits the payment information to a server computer of the related service of the related app for which the app information is proposed on the user terminal or to the related app;
Including,
If the user does not select the application information, when the payment information is sent directly or indirectly from the payment destination to the related application, the payment information is reflected in the related service,
the transmitting unit transmits the payment information to the server computer of the related service or the related app when it is determined that the user has selected the app information before the payment information is transmitted from the payment destination to the related app .
Payment system. a payment information acquisition unit that acquires payment information regarding a payment after a user who uses a payment service completes a payment using a user terminal;
an application information acquisition unit that acquires application information about an associated application of an associated service related to the payment service, the application information being selected from a plurality of the associated applications;
a suggestion unit in the user terminal that suggests the app information of the selected related app to the user;
a necessity determination unit that determines whether or not it is necessary to transmit the payment information for the related service of the selected related application ;
a transmitting unit that, when the necessity determination unit determines that transmission of the payment information is unnecessary, does not transmit the payment information to a server computer of the related service of the selected related app or the related app , and, when the necessity determination unit determines that transmission of the payment information is necessary, transmits the payment information to the server computer of the related service of the selected related app or the related app ;
Payment systems, including : The related service is a service that accepts adjustments regarding the payment.
A payment system according to any one of claims 1 to 5. The payment system further includes an amount determination unit that determines whether a payment amount in the payment is equal to or greater than a predetermined amount,
When it is determined that the payment amount is equal to or greater than the predetermined amount, the transmission unit transmits the payment information to the server computer of the related service or the related app .
A payment system according to any one of claims 1 to 5. a payment information acquisition unit that acquires payment information regarding a payment after a user who uses a payment service completes a payment using a user terminal;
a payment method determination unit that determines whether the payment method used in the payment is a predetermined payment method ;
a transmitting unit that transmits the payment information to a server computer or a related application of a related service related to the payment service when it is determined that the payment means is the predetermined payment means;
Payment systems, including : The payment system includes:
an application information acquisition unit that acquires application information related to the related application;
a proposal unit that proposes the app information to the user on a payment completion screen that is displayed on the user terminal after the payment is completed;
The payment system of claim 8 further comprising: The payment completion screen not only allows the user to propose the app information but also allows the user to input input information,
the transmission unit transmits the payment information and the input information to the server computer or the related application.
The payment system according to claim 9. The payment system includes:
an application information acquisition unit that acquires application information related to the related application;
a suggestion unit that determines whether the payment satisfies a predetermined condition and suggests the app information to the user on the user terminal based on the result of the determination;
The payment system according to any one of claims 8 to 10, further comprising: the proposal unit determines whether the payment amount of the payment is equal to or greater than a threshold, thereby determining whether the payment satisfies the predetermined condition;
The payment system of claim 11. a payment information acquisition step of acquiring payment information regarding a payment after a user who uses the payment service completes a payment using the user terminal;
an app information acquisition step of acquiring app information related to an app associated with a related service related to the payment service;
a proposing step of proposing the app information to the user on a payment completion screen displayed on the user terminal when the payment is completed;
a transmitting step of transmitting the payment information to a server computer of the related service of the related app for which the app information is proposed at the user terminal or to the related app ;
A transmission method including: a payment information acquisition unit that acquires payment information regarding a payment after a user who uses the payment service completes a payment using the user terminal;
an application information acquisition unit that acquires application information related to an application of a related service related to the payment service;
a proposal unit that proposes the app information to the user on a payment completion screen that is displayed on the user terminal when the payment is completed;
a transmission unit that transmits the payment information to a server computer of the related service of the related app for which the app information is proposed on the user terminal or to the related app ;
A program that allows a computer to function as a