JP7615115B2 - Payment system, processing execution method, and program - Google Patents

Description

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

In recent years, payment services that use electronic payment methods have become widespread. For example, Patent Document 1 describes a technology in which a server that centrally manages electronic money issued by each of a number of issuers receives electronic money usage logs from each of a number of affiliated stores. The server in Patent Document 1 executes cash settlement after the electronic money has been used, based on the usage logs received from the affiliated stores.

JP 2003-141428 A

However, with the technology of Patent Document 1, a user can only use electronic money of the issuer with which the affiliated store that the user visits has a contract. For example, if affiliated store X has a contract with Issuer A but not with Issuer B, only electronic money of Issuer A can be used at affiliated store X. This is the same for other conventional technologies and is not limited to the technology of Patent Document 1. For this reason, conventional technologies have not been able to sufficiently improve convenience for users who can use multiple payment methods.

One of the objectives of this disclosure is to increase convenience for users who can use multiple payment methods.

The payment system according to the present disclosure includes an association unit that associates first identification information capable of identifying a first payment means with second identification information capable of identifying a second payment means, and a second processing execution unit that executes a second process to use the second payment means identified by the second identification information associated with the first identification information when an IC chip storing the first identification information is read by a payment terminal that does not support the second payment means.

This disclosure improves convenience for users who can use multiple payment methods.

FIG. 1 is a diagram illustrating an example of the overall configuration of a payment system. A diagram showing an example of settings made to link the first payment method and the second payment method. FIG. 13 is a diagram showing an example of how a user uses an IC card of a first payment means to use a second payment means. A functional block diagram showing an example of functions realized in the payment system. FIG. 2 is a diagram showing an example of a first payment method database. FIG. 11 is a diagram showing an example of a second payment method database. FIG. 13 is a diagram illustrating an example of an association database. FIG. 2 is a diagram illustrating an example of a process executed in the payment system. FIG. 2 is a diagram illustrating an example of a process executed in the payment system. FIG. 13 is a diagram illustrating an example of a function realized in a modified example. FIG. 13 is a diagram illustrating an example of an association database according to the first modified example. FIG. 13 is a diagram showing an example of auto-charging in modified example 4.

[1. Overall configuration of the payment system]
An example of an embodiment of a payment system according to the present disclosure will be described. FIG. 1 is a diagram showing an example of the overall configuration of a payment system. For example, a payment system 1 includes a payment server 10. The payment system 1 cooperates with a linked system 2. Here, cooperation means performing information processing for a common purpose. Communication with each other to perform a certain information processing corresponds to cooperation. The linked system 2 includes a linked server 20. Each of the payment server 10 and the linked server 20 can be connected to a network N such as the Internet or a LAN. A user terminal 30 and a payment terminal 40 can also be connected to the network N.

The payment server 10 is a server computer of a payment service provider. A payment service provider is a business that provides payment services. The payment service is a service related to electronic payment (cashless payment). 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 a volatile memory such as a RAM, and a non-volatile memory such as a 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 associated server 20 is a server computer of the associated party. Although the associated server 20 is called a server, it may actually be a personal computer. The associated party is an organization that associates with the payment service provider. For example, the associated party may be another payment service provider, or a business other than the payment service provider. It may be the same as the payment service provider that manages the payment server 10. The associated party may be an affiliate of the payment service provider that manages the payment server 10, or a company with which there is no capital relationship.

For example, the associated server 20 includes a control unit 21, a memory unit 22, and a communication unit 23. The physical 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. A computer used in a technology called a thin client may correspond to the associated server 20. For example, the associated server 20 communicates with the payment server 10 every time a payment is made. The associated server 20 may communicate with the payment server 10 at other times, for example, it may communicate with the payment server 10 periodically, or it may communicate with the payment server 10 when some operation is performed.

The user terminal 30 is a user's computer. In this embodiment, the end user of the payment service, not the affiliated store of the payment service, is described as the user. For example, the user terminal 30 is a smartphone, a tablet terminal, a wearable terminal, or a personal computer. For example, the user terminal 30 includes a control unit 31, a memory unit 32, a communication unit 33, an operation unit 34, and a display unit 35. The physical 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 liquid crystal or organic EL display.

The payment terminal 40 is a computer used for payment. For example, the payment terminal 40 is a POS (Point Of Sales) terminal, a vending machine, an automatic ticket gate, a personal computer, a tablet terminal, or a smartphone. For example, the payment terminal 40 includes a control unit 41, a memory unit 42, a communication unit 43, an operation unit 44, and a display unit 45. The physical 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.

In this embodiment, a reader/writer 46 is connected to the payment terminal 40. The reader/writer 46 may be built into the payment terminal 40. The reader/writer 46 is a device that reads and writes to an information storage medium. The information storage medium may be any medium capable of storing any information, such as an IC card, an IC chip included in the user terminal 30, a magnetic card, or a memory. A reader device that has a reading function but no writing function may be connected to the payment terminal 40.

The programs stored in the storage units 12, 22, 32, and 42 may be supplied via the network N. Also, the programs stored in a computer-readable information storage medium may be supplied via a reading unit (e.g., an optical disk drive or a memory card slot) that reads the information storage medium, or an input/output unit (e.g., a USB port) that inputs and outputs data to and from an external device.

Furthermore, each of the payment system 1 and the associated system 2 only needs to include at least one computer, and is not limited to the example of FIG. 1. For example, the payment system 1 may include a payment server 10 and another server computer. The processing of the associated server 20 may be executed by the other server computer. In this case, the associated system 2 may not exist. The payment system 1 may include a payment server 10 and a terminal operated by a person in charge of the payment service provider.

[2. Overview of the payment system]
In this embodiment, a user can use multiple payment means. A payment means is a means used for payment. In this embodiment, a payment means used for electronic payment is described. A payment means is sometimes called a payment means. A payment means is sometimes called an electronic value, meaning that it has electronic value. A payment means may be of any type, and may be, for example, electronic money, points, an account (including a bank account), a wallet, cryptocurrency, a credit card, a debit card, or a means called by any other name. A payment means is not limited to those for which a concept of a balance exists, and may be those for which a concept of a balance does not exist.

In this embodiment, an example is given of a case where a user uses two payment means, a first payment means and a second payment means. Furthermore, IC card-type electronic money is described as an example of the first payment means. Online-type electronic money is described as an example of the second payment means. The combination of the first payment means and the second payment means may be any combination and is not limited to the example of this embodiment. Other combination examples will be described in the modified examples described later. The user may be able to use three or more payment means. Hereinafter, when there is no need to distinguish between the first payment means and the second payment means, they will simply be referred to as payment means.

For example, payment terminal 40 supports a first payment method, but does not support a second payment method. Supporting a payment method means that the payment method can be used. For example, having both the hardware (equipment) and software (function) for using a payment method is equivalent to supporting a payment method. If at least one of the hardware and software is not present, in principle, payment cannot be used, and therefore the payment method is not supported. When payment terminal 40 is placed in a store, the store being an affiliated store for the payment method is equivalent to supporting the payment method.

For example, the payment terminal 40 can read an IC card of the first payment means with the reader/writer 46, but cannot read information for using the second payment means (e.g., a two-dimensional code or barcode displayed on the display unit 35) with the reader/writer 46. In conventional technology, a payment terminal 40 that does not support the second payment means cannot use the second payment means, but in this embodiment, the first payment means and the second payment means are linked, making it possible to use the second payment means. However, the user must make the settings in advance.

Figure 2 is a diagram showing an example of settings performed to link the first payment means and the second payment means. For example, when a user operates the user terminal 30 to access the payment server 10, a home screen SC1, which is the website of the first payment means, is displayed on the display unit 35. In this embodiment, a case is described in which the home screen SC1 is displayed in a browser, but the home screen SC1 may also be displayed in an application dedicated to the first payment means.

In the example of FIG. 2, "AAA Money" corresponds to the first payment method. "BBB Cash" corresponds to the second payment method. It is assumed that the user has previously associated the first identification information capable of identifying the first payment method with the second identification information capable of identifying the second payment method. Details of the first identification information and the second identification information will be described later. For example, when the user selects button B10, a modal M11 for guiding the user to start setting is displayed on the home screen SC1. When the user selects button B12, a modal M13 for specifying the setting contents is displayed on the home screen SC1.

In this embodiment, an example is given of a case where there are two settings: a usage necessity setting and a priority usage setting. The usage necessity setting is a setting regarding whether or not to use the second payment method. For example, the usage necessity setting is either a first value indicating that the second payment method is used, or a second value indicating that the second payment method is not used. In the example of FIG. 2, when the user turns on button B14, the usage necessity setting becomes the first value. When the user turns off button B14, the usage necessity setting becomes the second value.

The priority usage setting is a setting related to which of the first and second payment methods is to be used preferentially. For example, the priority usage setting is either a first value indicating that the first payment method is to be used preferentially, or a second value indicating that the second payment method is to be used preferentially. In the example of FIG. 2, when the user selects button B15, the priority usage setting becomes the first value. When the user selects button B16, the priority usage setting becomes the second value.

For example, using the first payment means without using the second payment means corresponds to preferentially using the first payment means. In other words, not using the second payment means when a payment can be completed using only the first payment means corresponds to preferentially using the first payment means. When the first and second payment means are used in combination, the use of the first payment means in an amount greater than the use of the second payment means may correspond to preferentially using the first payment means.

For example, using the second payment means without using the first payment means corresponds to preferentially using the second payment means. In other words, not using the first payment means when payment can be completed using only the second payment means corresponds to preferentially using the second payment means. When using both the first and second payment means, the usage amount of the second payment means being greater than the usage amount of the first payment means may correspond to preferentially using the second payment means.

For example, suppose that the user turns on button B14 and selects button B16. In this state, when the user closes modal M13, information indicating that the second payment method will be used and that the second payment method will be used preferentially (in the example in the lower right of FIG. 2, the text "Use BBB Cash (BBB Cash preferred)") is displayed on the home screen SC1. Furthermore, in addition to the balance of the first payment method, the total balance of the first payment method and the second payment method is displayed on the home screen SC1.

Figure 3 is a diagram showing an example of how a user uses an IC card of a first payment means to use a second payment means. For example, the user holds IC card C of the first payment means over reader/writer 46. Various information for using the first payment means is recorded on IC card C, but in principle, information for using the second payment means (such as the second identification information and the balance of the second payment means described below) is not recorded. At least in the memory area of IC card C that is read at the time of payment, information for using the second payment means is not recorded. Some information related to the second payment means may be recorded in other areas.

For example, when the reader/writer 46 reads the IC card C, the payment terminal 40 communicates with the associated server 20, and the process required for payment is executed. Details of this process will be described later. In the example of FIG. 3, the balance of the first payment means before payment is 600 yen. The balance of the second payment means before payment is 3000 yen. The payment amount is 1000 yen. For example, if the usage necessity setting indicates that the second payment means will not be used (the branch "Do not use BBB Cash" in the example of FIG. 3), an error occurs in the payment due to insufficient balance in the first payment means. Because the payment is an error, the balance of the first payment means and the balance of the second payment means remain unchanged.

For example, if the usage necessity setting indicates that the second payment method is to be used and the priority usage setting indicates that the first payment method is to be used preferentially (in the example of Figure 3, the branch "Use BBB Cash (AAA Money Priority)"), the balance of the first payment method, 600 yen, is used preferentially. Since the balance of the first payment method alone is not enough, the shortfall of 400 yen from the balance of the second payment method is used. After payment, the balance of the first payment method will be 0 yen. After payment, the balance of the second payment method will be 2600 yen.

For example, if the usage necessity setting indicates that the second payment method is to be used and the priority usage setting indicates that the second payment method is to be used preferentially (the branch "Use BBB Cash (BBB Cash Priority)" in the example of Figure 3), the balance of the second payment method, 3,000 yen, is used preferentially. Since the balance of the second payment method is sufficient, the balance of the first payment method is not used. The balance of the first payment method after payment remains unchanged at 600 yen. The balance of the second payment method after payment becomes 2,000 yen.

As described above, in this embodiment, even if the payment terminal 40 does not support the second payment means, the second payment means can be used by holding the IC card C of the first payment means over the payment terminal 40. This increases user convenience, as the second payment means can be used if the IC card C of the first payment means is available, even if the payment terminal 40 does not support the second payment means. The details of the payment system 1 will be described below.

[3. Functions Realized by the Payment System]
FIG. 4 is a functional block diagram showing an example of functions realized by payment system 1.

[3-1. Functions realized by the payment server]
For example, the payment server 10 includes a data storage unit 100, an association unit 101, a use necessity setting unit 102, a priority usage setting unit 103, a receiving unit 104, a first process execution unit 105, a second process execution unit 106, and a storage unit 107. The data storage unit 100 is realized by the storage unit 12. The association unit 101, the use necessity setting unit 102, the priority usage setting unit 103, the receiving unit 104, the first process execution unit 105, the second process execution unit 106, and the storage unit 107 are realized by the control unit 11.

[Data storage unit]
The data storage unit 100 stores data necessary for providing payment services. For example, the data storage unit 100 stores a first payment method database DB1, a second payment method database DB2, and an association database DB3.

Figure 5 is a diagram showing an example of the first payment means database DB1. The first payment means database DB1 is a database in which information related to the first payment means is stored. For example, the first payment means database DB1 stores first identification information, balance, usage history information, and charge history information. The first payment means database DB1 may also store other information related to the first payment means. The information stored in the first payment means database DB1 is not limited to the example of Figure 5. For example, the first payment means database DB1 may also store other information such as information related to other payment means used to charge the first payment means.

The first identification information is information that can identify the first payment means. For example, the first identification information is an ID or number of the first payment means that is issued so as not to overlap with other first identification information. The first identification information is expressed by letters, numbers, symbols, or a combination of these. The first identification information is not limited to the ID or number of the first payment means. For example, the first identification information may be an email address or telephone number of a user who owns the first payment means. When a charge or payment is made to the first payment means of a certain first identification information, the balance associated with this first identification information changes. The balance associated with the first identification information may have restrictions on the stores or products that can be used.

Usage history information is information about the usage history of a first payment means. For example, usage history information indicates the date and time of use, the location of use, the payment amount, and the balance after payment. When a first payment means with certain first identification information is used, usage history information is generated and associated with this first identification information. Charge history information is information about the history of charging the first payment means. For example, charge history information indicates the date and time of charge, the charge method, the charge amount, and the balance after charge. When a charge is executed with a first payment means with certain first identification information, charge history information is generated and associated with this first identification information.

Figure 6 is a diagram showing an example of the second payment means database DB2. The second payment means database DB2 is a database in which information related to the second payment means is stored. For example, the second payment means database DB2 stores second identification information, balance information, usage history information, and charge history information. The second payment means database DB2 may also store other information related to the second payment means. The information stored in the second payment means database DB2 is not limited to the example of Figure 6. For example, the second payment means database DB2 may also store other information such as information related to the payment means used to charge the second payment means.

The second identification information is information capable of identifying the second payment means. The second identification information is an ID or number of the second payment means that is issued so as not to overlap with other second identification information. The second identification information is expressed by letters, numbers, symbols, or a combination of these. The second identification information is not limited to the ID or number of the second payment means. For example, the second identification information may be the email address or telephone number of the user who holds the second payment means.

In the example of FIG. 6, the second identification information is the email address of the user who owns the second payment means. This email address may be used not only when the user logs in to the service of the second payment means, but also when the user logs in to the service of the first payment means. In other words, the information for logging in may be the same for the first payment means and the second payment means. When a charge or payment is made to the second payment means of a certain second identification information, the balance associated with this second identification information changes. The balance associated with the second identification information may have restrictions on the stores or products that can be used.

Usage history information is information relating to the usage history of the second payment means. For example, the usage history information indicates the date and time of use, the location of use, the payment amount, and the balance after payment. When a second payment means with certain second identification information is used, usage history information is generated and associated with this second identification information. Charge history information is information relating to the charge history of the second payment means. For example, the charge history information indicates the date and time of charge, the charge method, the charge amount, and the balance after charge. When a charge is executed with a second payment means with certain second identification information, charge history information is generated and associated with this second identification information.

Figure 7 is a diagram showing an example of the association database DB3. The association database DB3 is a database showing the association of the first identification information and the second identification information. For example, the association database DB3 stores the first identification information, the second identification information, a usage necessity setting, and a priority usage setting. The information stored in the association database DB3 is not limited to the example of Figure 7. For example, the association database DB3 may store only the first identification information and the second identification information. The first identification information and the second identification information may be associated with the first payment means database DB1 or the second payment means database DB2, rather than with the association database DB3.

For example, when a user performs an operation to link the first payment means and the second payment means, the payment server 10 creates a new record in the association database DB3. The payment server 10 stores the first identification information, the second identification information, the use necessity setting, and the priority use setting in the new record. The first identification information, the second identification information, the use necessity setting, and the priority use setting may be input by the user from the home screen SC1 or another screen. The first identification information and the second identification information may be read by the user terminal 30 instead of being manually input by the user.

The data stored in the data storage unit 100 is not limited to the above examples. The data storage unit 100 can store any data. For example, the data storage unit 100 may store display data for displaying the home screen SC1. When the home screen SC1 is displayed in a browser, the display data is HTML data. When the home screen SC1 is displayed in a dedicated application, the display data is image data used to display some kind of screen in the application.

[Association section]
The associating unit 101 associates first identification information capable of identifying a first payment means with second identification information capable of identifying a second payment means. Associating means making it possible to search for one piece of information from another piece of information. In this embodiment, storing the first identification information and the second identification information in the same record in the association database DB3 corresponds to associating the first identification information and the second identification information.

For example, when a user inputs first identification information and second identification information to be associated with each other from the home screen SC1 or another screen, the association unit 101 associates the input first identification information and second identification information by storing the input first identification information and second identification information in the association database DB3. The first identification information and second identification information to be associated with each other may be input by the payment service provider, rather than by the user.

[Use necessity setting section]
The use necessity setting unit 102 performs a use necessity setting regarding whether or not to use the second payment method. Performing a use necessity setting means recording the content of the use necessity setting specified by the user. In this embodiment, since the use necessity setting is stored in the association database DB3, the use necessity setting unit 102 stores the use necessity setting specified by the user in the association database DB3.

For example, before displaying the home screen SC1, the user logs in to the first payment service, which is the payment service of the first payment method. The login allows the payment server 10 to identify the first identification information of the first payment method used by the user. The usage necessity setting unit 102 stores the first identification information of the first payment method used by the logged-in user and the usage necessity setting specified by the user on the home screen SC1 in the association database DB3.

[Priority Use Setting Section]
The priority usage setting unit 103 sets a priority usage setting for the first payment means or the second payment means to be used preferentially. Setting a priority usage setting means recording the contents of the priority usage setting specified by the user. In this embodiment, the priority usage setting is stored in the association database DB3, so the priority usage setting unit 103 stores the priority usage setting specified by the user in the association database DB3.

For example, the user logs in to the first payment service before displaying the home screen SC1. The usage necessity setting unit 102 stores in the association database DB3 the first identification information of the first payment method used by the logged-in user and the priority usage setting specified by the user on the home screen SC1. The priority usage setting may specify the usage amount of the preferred payment method. For example, it may be possible to set the priority usage to be such that the second payment method is used preferentially up to 1,000 yen, and the first payment method is used for amounts exceeding 1,000 yen.

[Receiver]
The receiving unit 104 receives various data from the cooperating server 20. The receiving unit 104 may receive various data from the user terminal 30 or the payment terminal 40. In this embodiment, when the second payment means is used, the first payment means is charged from the second payment means, and then the first payment means is used. Furthermore, when the first identification information is read by the payment terminal 40, this charging is performed by the cooperating system 2 that cooperates with the payment system 1.

For example, the receiving unit 104 receives second execution data related to the execution result of the charge from the linked system 2. The second execution data indicates the extent to which the second payment means was used by the charge. For example, the second execution data includes the date and time of the charge and the charge amount. When the payment execution unit 202 of the linked system 2 described later executes a charge from the second payment means to the first payment means, it generates second execution data and transmits it to the payment server 10. The receiving unit 104 receives the second execution data from the linked system 2.

[First processing execution unit]
The first process execution unit 105 executes a first process for using the first payment means. The first process is a process for reducing the balance of the first payment means. In this embodiment, since the balance of the first payment means is stored in the first payment means database DB1, the first process execution unit 105 executes the first process by reducing the balance of the first payment means stored in the first payment means database DB1.

In this embodiment, the payment server 10 does not communicate directly with the payment terminal 40. The payment terminal 40 communicates directly with the partner server 20. The payment execution unit 202 of the partner server 20, which will be described later, executes a payment using the first payment means based on the content of the communication with the payment terminal 40. The receiving unit 104 receives first execution data related to the execution result of the payment using the first payment means from the partner server 20. For example, the first execution data indicates the first identification information, the payment location, the payment amount, and the payment date and time.

For example, the first process execution unit 105 reduces the balance of the first payment means in the first payment means database DB1 associated with the first identification information indicated by the first execution data by the payment amount indicated by the first execution data. The first execution data may indicate the balance of the first payment means after payment. In this case, the first process execution unit 105 updates the balance of the first payment means in the first payment means database DB1 associated with the first identification information indicated by the first execution data so that it matches the balance of the first payment means after payment indicated by the first execution data. All or part of this series of processes corresponds to the first process.

In this embodiment, the first process execution unit 105 executes the first process when the preferred usage setting indicates the second payment means and the balance of the second payment means is insufficient. The first process execution unit 105 executes the first process so that the balance of the first payment means is reduced by the shortfall in the balance of the second payment means. The shortfall is indicated in the first execution data received by the receiving unit 104 from the linked server 20. The first process execution unit 105 executes the first process so that the balance of the first payment means is reduced by the shortfall indicated in the first execution data. The first execution data may indicate the balance of the first payment means after the shortfall is deducted. In this case, the first process execution unit 105 may update the balance of the first payment means associated with the first identification information indicated by the first execution data in the first payment means database DB1 so that it matches the balance of the first payment means after the shortfall indicated by the first execution data is deducted.

For example, the first process execution unit 105 executes the first process even when the preferred use setting indicates the first payment means. The first process execution unit 105 executes the first process even when the use necessity setting indicates that the second payment means is not to be used. The first process execution unit 105 executes the first process even when a user who has not linked the first and second payment means uses the first payment means. These first processes may be executed based on the first execution data received by the receiving unit 104 from the linked server 20. In this embodiment, even when the use necessity setting indicates that the second payment means is to be used and the balance of the second payment means is sufficient, the first payment means is charged from the second payment means and the balance of the first payment means is reduced. Therefore, even in this case, the first process execution unit 105 executes the first process to reduce the balance of the first payment means.

The payment server 10 may communicate directly with the payment terminal 40, rather than through the associated server 20. In this case, the payment server 10 receives a payment request from the payment terminal 40. The payment request is data in a predetermined format for requesting execution of a payment. For example, the payment request includes the first identification information and the payment amount. The first processing execution unit 105 executes the first processing by reducing the balance of the first payment means associated with the first identification information indicated by the payment request by the payment amount indicated by the payment request. The first processing itself may be other processing used in known payment services. The payment request may include information that can identify the payment terminal 40, or information about the product purchased by the user.

[Second processing execution unit]
The second process execution unit 106 executes a second process to use the second payment means. The second process is a process to reduce the balance of the second payment means. In this embodiment, since the balance of the second payment means is stored in the second payment means database DB2, the second process execution unit 106 executes the second process by reducing the balance of the second payment means stored in the second payment means database DB2. Note that the second process execution unit 106 does not execute the second process if the usage necessity setting indicates that the second payment means will not be used.

In this embodiment, the payment server 10 does not communicate directly with the payment terminal 40, so the payment execution unit 202 of the associated server 20 (described later) executes the payment using the second payment means based on the content of the communication with the payment terminal 40. The receiving unit 104 receives second execution data related to the execution result of the payment using the second payment means from the associated server 20. For example, the second execution data indicates the second identification information, the payment location, the payment amount, and the payment date and time.

For example, the second process execution unit 106 reduces the balance of the second payment means in the second payment means database DB2 associated with the second identification information indicated by the second execution data by the payment amount indicated by the second execution data. The second execution data may indicate the balance of the second payment means after the payment. In this case, the second process execution unit 106 updates the balance of the second payment means in the second payment means database DB2 associated with the second identification information indicated by the second execution data so that it matches the balance of the second payment means after the payment indicated by the second execution data. All or part of this series of processes corresponds to the second process.

In this embodiment, when an IC chip storing the first identification information is read by a payment terminal 40 that does not support the second payment means, the second process execution unit 106 executes a second process for using the second payment means identified by the second identification information associated with the first identification information. For example, the second process execution unit 106 executes the second process when an IC card C including an IC chip is read by the payment terminal 40.

The first identification information may be stored in an information storage medium other than the IC card C. For example, the first identification information may be stored in an IC chip of the user terminal 30. The first identification information may be stored in an information storage medium other than an IC chip. The first identification information may be stored in a magnetic card instead of an IC chip. The first identification information may be stored in a communication device capable of short-range wireless communication instead of a card. The first identification information may be stored in an IC tag.

The first identification information may also be printed on the face of the card rather than being stored in an information storage medium. In this case, the payment terminal 40 reads the first identification information printed on the face of the card by photographing it with a camera. Furthermore, the first identification information may be coded using a barcode or a two-dimensional code. In this case, the payment terminal 40 reads the coded first identification information with a code reader or a camera.

As described above, other modes are also possible besides the mode in which the IC chip storing the first identification information is read. In the case of other modes, when the first identification information is read by the payment terminal 40 using any of the reading methods described above, the second process execution unit 106 executes a second process for using the second payment means identified by the second identification information associated with the first identification information.

In this embodiment, the second execution data indicates the second identification information associated with the first identification information read by the payment terminal 40. The second processing execution unit 106 reduces the balance of the second payment means associated with the second identification information indicated by the second execution data by the payment amount indicated by the second execution data. For example, the second processing execution unit 106 executes the second processing when the preferred usage setting indicates the second payment means. The second processing execution unit 106 executes the second processing based on the second execution data received from the linked server 20 when the preferred usage setting indicates the second payment means. The second processing execution unit 106 may not execute the second processing when the preferred usage setting indicates the first payment means. In this case, the payment using both the first payment means and the second payment means will not be executed. In this case, the usability setting may not exist.

For example, the second process execution unit 106 executes the second process when the preferred usage setting indicates the first payment means and the balance of the first payment means is insufficient. The second process execution unit 106 executes the second process so that the balance of the second payment means is reduced by the shortfall in the balance of the first payment means. The shortfall is indicated in the second execution data received by the receiving unit 104 from the linked server 20. The second process execution unit 106 executes the second process so that the balance of the second payment means is reduced by the shortfall indicated in the second execution data. The second execution data may indicate the balance of the second payment means after the shortfall is deducted. In this case, the second process execution unit 106 may update the balance of the second payment means associated with the second identification information indicated by the second execution data in the second payment means database DB2 so that it matches the balance of the second payment means after the shortfall is deducted indicated by the second execution data.

In this embodiment, when the first identification information is read by the payment terminal 40, a charge is made to the first payment means using the second payment means. Furthermore, a payment is made based on the first payment means after the charge is made. Therefore, the second process is a process of deducting an amount corresponding to the charge from the balance of the second payment means. The payment amount indicated by the second execution data means the charge amount. The second process execution unit 106 executes the second process based on the second execution data. The second process execution unit 106 executes the second process by deducting the balance of the second payment means associated with the second identification information indicated by the second execution data in the second payment means database DB2 by the charge amount indicated by the second execution data.

In this embodiment, the user uses the first payment method by using an IC card C, so the second process execution unit 106 executes the second process when the IC card C storing the first identification information is read by the payment terminal 40. The first identification information may be stored in an information storage medium other than the IC card C. For example, the first identification information may be stored in the memory unit 32 or IC chip of the user terminal 30.

The first identification information may be stored on a magnetic card instead of the IC card C. The first identification information may be printed on the face of the card. In this case, the payment terminal 40 reads the first identification information printed on the face of the card by photographing it with a camera. Furthermore, the first identification information may be coded using a barcode or a two-dimensional code. In this case, the payment terminal 40 reads the coded first identification information with a code reader or a camera.

The payment server 10 may also communicate directly with the payment terminal 40, rather than through the associated server 20. In this case, the payment server 10 receives a payment request from the payment terminal 40. The payment request is data in a predetermined format for requesting execution of a payment. For example, the payment request includes the second identification information and the payment amount. The second processing execution unit 106 executes the second processing by reducing the balance of the second payment means associated with the second identification information indicated by the payment request by the payment amount indicated by the payment request. The second processing itself may be other processing used in known payment services.

[Storage section]
When a charge is performed, the storage unit 107 stores second history data indicating that the charge was performed using the second payment means in the first payment means database DB1 in association with the first identification information. The second history data is data related to the charge to the first payment means when the second payment means is used. For example, the second history data indicates the charge date and time, the charge method, the charge amount, and the balance after charge. Since the charge method indicates the payment means used in the charge, here, the second identification information of the second payment means used in the charge is shown.

In this embodiment, the storage unit 107 stores the second history data in the first payment means database DB1 as charge history information. For example, when the associated server 20 executes a charge from the second payment means to the first payment means, it generates second history data and transmits it to the payment server 10. This second history data is associated with first identification information of the first payment means from which the charge was executed. The storage unit 107 stores the second history data in the first payment means database DB1 as charge history information, in association with the first identification information received from the associated server 20.

In this embodiment, the payment terminal 40 reads an information storage medium (e.g., IC card C) that stores the first identification information. This information storage medium is assumed to record first history data indicating that a charge was performed using the second payment means. The first history data indicates the same content as the second history data. For example, the first history data indicates the charge date and time, the charge method, the charge amount, and the balance after charge. The charge method indicates the second identification information of the second payment means used for the charge.

[3-2. Functions realized by the partner server]
The cooperating server includes a data storage unit 200, a payment request receiving unit 201, and a payment execution unit 202. The data storage unit 200 is realized by the storage unit 22. The payment request receiving unit 201 and the payment execution unit 202 are realized by the control unit 21.

[Data storage section]
The data storage unit 200 stores data necessary for providing a payment service. For example, the data storage unit 200 stores an association database DB3. The association database DB3 stored in the data storage unit 200 may be the same as the association database DB3 stored in the data storage unit 100. The consistency of the association database DB3 between the payment server 10 and the cooperating server 20 may be maintained periodically or irregularly.

The data storage unit 200 may store a first payment method database DB1 and a second payment method database DB2. In this case, the first payment method database DB1 and the second payment method database DB2 may be maintained consistent between the payment server 10 and the associated server 20 on a regular or irregular basis. The data storage unit 200 may also store other data necessary for the processing described in this embodiment.

[Payment request receiving unit]
The payment request receiving unit 201 receives a payment request from the payment terminal 40. In this embodiment, the payment request receiving unit 201 receives the payment request from the payment terminal 40 when the IC card C is read by the payment terminal 40.

[Payment Execution Department]
The payment execution unit 202 executes the payment based on the payment request received from the payment terminal 40. In this embodiment, the payment request received from the payment terminal 40 that does not support the second payment means includes the first identification information. For example, the payment execution unit 202 refers to the association database DB3 stored in the data storage unit 200 and determines whether the first identification information included in the payment request is associated with the second identification information. If it is determined that the first identification information included in the payment request is not associated with the second identification information, the payment execution unit 202 executes the payment using the first payment means in the same manner as in the past.

For example, if it is determined that the second identification information is associated with the first identification information included in the payment request, the payment execution unit 202 refers to the association database DB3 and acquires the usage necessity setting associated with the first identification information and the second identification information. If the usage necessity setting indicates that the second payment method is not to be used, the payment execution unit 202 executes the payment using the first payment method in the same manner as in the past.

For example, if the usage necessity setting indicates that the second payment method is to be used, the payment execution unit 202 refers to the association database DB3 and obtains the priority usage setting stored in the same record as the usage necessity setting. Furthermore, the payment execution unit 202 sends a reference request to the payment server 10 to reference the balance of the first payment method and the balance of the second payment method. If the first payment method database DB1 and the second payment method database DB2 are stored in the data storage unit 200, these databases can be referenced without sending a reference request.

For example, the reference request includes first identification information and second identification information to be referenced for the balance. The payment server 10 references the first payment method database DB1 and obtains the balance of the first payment method associated with the first identification information included in the reference request. The payment server 10 references the second payment method database DB2 and obtains the balance of the second payment method associated with the second identification information included in the reference request. The payment server 10 transmits the balance of the first payment method and the balance of the second payment method to the partner server 20.

Incidentally, since the balance of the first payment means is written to the IC card C, the associated server 20 does not need to inquire about the balance of the first payment means from the payment server 10. In this case, the reference request does not include the first identification information. The associated server 20 obtains the balance of the first payment means written to the IC card C from the payment terminal 40. The payment execution unit 202 may execute the payment based on the balance of the first payment means obtained from the payment terminal 40. Furthermore, the balance of the first payment means may not be stored in the payment server 10 and the associated server 20, and the balance of the first payment means may be written only to the IC card C.

In addition, if the balance of the first payment means is not written to the IC card C and is stored in the payment server 10, the cooperating server 20 only needs to obtain the balance of the first payment means from the payment server 10 by a reference request. In addition, if the balance of the first payment means is not written to the IC card C and is stored in the cooperating server 20, the cooperating server 20 only needs to obtain the balance of the first payment means stored by itself.

For example, the cooperating server 20 receives the balance of the first payment means and the balance of the second payment means from the payment server 10. The payment execution unit 202 executes the payment based on these balances and the payment amount included in the payment request. If the first payment means is indicated in the preferred usage setting, the payment execution unit 202 determines whether or not the first payment means alone is sufficient based on the balance of the first payment means and the payment amount included in the payment request. If it is determined that the first payment means alone is sufficient, the payment execution unit 202 executes the payment using the first payment means in the same manner as in the past.

For example, if it is determined that the first payment means is insufficient, the payment execution unit 202 determines whether the total of the balance of the first payment means and the balance of the second payment means is equal to or greater than the payment amount included in the payment request. If the payment execution unit 202 determines that the total is less than the payment amount, it treats it as an error due to insufficient balance. The processing of errors due to insufficient balance can itself be performed using publicly known processing. If the payment execution unit 202 determines that the total is equal to or greater than the payment amount, it executes a charge from the second payment means to the first payment means.

For example, the payment execution unit 202 calculates the shortfall of the first payment means by subtracting the balance of the first payment means from the payment amount included in the payment request. The payment execution unit 202 uses the balance of the second payment means to charge the first payment means by the shortfall. The charge itself can be performed using a known process. The balance of the second payment means is reduced by the amount of the charge. The payment execution unit 202 executes the payment based on the first payment means after the charge. The balance of the first payment means after the payment becomes zero.

For example, the payment execution unit 202 generates the first and second execution data described above based on the results of the charge and payment execution, and transmits them to the payment server 10. The payment execution unit 202 transmits a notification to the payment terminal 40 indicating that the payment has been completed. This notification itself is the same as when payment is made using only the first payment means. For this reason, the communication between the cooperating server 20 and the payment terminal 40 can use the same mechanism as when payment is made using only the first payment means. For example, the format of the data transmitted between the cooperating server 20 and the payment terminal 40 (for example, the API format) is the same as when payment is made using only the first payment means.

For example, when the second payment means is indicated in the priority usage setting, the payment execution unit 202 determines whether the second payment means alone is sufficient based on the balance of the second payment means and the payment amount included in the payment request. If it is determined that the second payment means alone is sufficient, the payment execution unit 202 charges the first payment means by the payment amount based on the balance of the second payment means. The balance of the second payment means is reduced by the charged amount. The payment execution unit 202 executes the payment based on the first payment means after charging. The balance of the first payment means after the payment remains the same as before the payment. As described above, the first execution data and the second execution data are generated and a notification is sent to the payment terminal 40.

For example, if it is determined that the second payment means alone is insufficient, the payment execution unit 202 determines whether the total of the balance of the first payment means and the balance of the second payment means is equal to or greater than the payment amount included in the payment request. If the payment execution unit 202 determines that the total is less than the payment amount, it treats it as an error due to insufficient balance. The processing of errors due to insufficient balance can itself be performed using publicly known processing. If the payment execution unit 202 determines that the total is equal to or greater than the payment amount, it executes a charge from the second payment means to the first payment means.

For example, the payment execution unit 202 charges the first payment means with the full amount of the second payment means. The balance of the second payment means becomes zero. The payment execution unit 202 executes the payment based on the first payment means after charging. The balance of the first payment means after the payment is reduced by the shortfall. As described above, the first execution data and the second execution data are generated, and a notification is sent to the payment terminal 40.

Note that the balance of the first payment means may be used in combination with the balance of the second payment means without charging the first payment means from the second payment means. In this case, the payment execution unit 202 may reduce both the balance of the first payment means and the balance of the second payment means without charging the first payment means from the second payment means. The payment execution unit 202 may reduce the balance of the second payment means without charging the first payment means from the second payment means.

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

[Data storage section]
The data storage unit 300 stores data necessary for using the payment service. For example, the data storage unit 300 stores a browser or a dedicated application.

[Display control unit]
The display control unit 301 causes various screens to be displayed on the display unit 35. For example, the display control unit 301 causes the display unit 35 to display a home screen SC1.

[Operation reception section]
The operation reception unit 302 receives various operations by the user. For example, the operation reception unit 302 receives an operation on the home screen SC1.

[3-4. Functions realized by the payment terminal]
The payment terminal 40 includes a data storage unit 400, an acquisition unit 401, and a payment request transmission unit 402. The data storage unit 400 is realized by the storage unit 42. The acquisition unit 401 and the payment request transmission unit 402 are realized by the control unit 41.

[Data storage section]
The data storage unit 400 stores data necessary for providing a payment service. For example, the data storage unit 400 stores a program for generating and transmitting a payment request.

[Acquisition section]
The acquisition unit 401 acquires the first identification information read by the payment terminal 40. The method of reading the first identification information itself can use various known methods. For example, a method using magnetism, a method using electromagnetic waves, a method using short-range wireless communication, a method using optically reading an image, a method using sound, or other methods may be used. The payment terminal 40 may include or be connected to devices required for these methods. For example, the payment terminal 40 may include or be connected to a reader terminal, a wireless receiver, a camera, a scanner, a microphone, or other devices in addition to the reader/writer 46.

In this embodiment, since the first identification information is stored in the IC card C, the acquisition unit 401 acquires the first identification information stored in the IC card C. For example, the payment terminal 40 has a function of not only reading the IC card C but also writing to the IC card C. Information such as payment history and charge history is written to the IC card C. When a charge is executed from the second payment means to the first payment means at the time of payment, the charge history of this charge is also written to the IC card C.

[Payment request transmission unit]
The payment request transmission unit 402 transmits a payment request to the payment server 10. For example, when an operation for payment is performed at the payment terminal 40 and the IC card C is read by the reader/writer 46, the payment request transmission unit 402 transmits a payment request to the payment server 10.

[4. Processing Executed by the Payment System]
Figures 8 and 9 are diagrams showing an example of a process executed in payment system 1. The process in Figures 8 and 9 is executed by control units 11, 21, 31, and 41 operating in accordance with programs stored in storage units 12, 22, 32, and 42, respectively.

As shown in FIG. 8, the user terminal 30 executes a login process with the payment server 10 to display the home screen SC1 on the display unit 35 (S1). The user terminal 30 executes a process for linking the first payment means and the second payment means with the payment server 10 (S2). In S2, the user inputs the first identification information, the second identification information, a linking necessity setting, and a priority use setting on the home screen SC1 or another screen. The payment server 10 associates the information entered by the user with each other and stores it in the association database DB3. The payment server 10 shares the association database DB3 with the linked server 20 (S3).

After that, the user can use the second payment means by using the IC card C of the first payment means with a payment terminal 40 that does not support the second payment means. When the user holds the IC card C over the reader/writer 46, the payment terminal 40 uses the reader/writer 46 to read the first identification information stored on the IC card C (S4). The payment terminal 40 transmits a payment request to the cooperating server 20 based on the first identification information read in S4 (S5). It is assumed that information other than the first identification information included in the payment request (such as the payment amount) has been input to the payment terminal 40 in advance. The other information may include information about the product the user is purchasing.

When the associated server 20 receives a payment request (S6), it determines whether or not the second identification information is associated with the first identification information included in the payment request based on the association database DB3 (S7). If it is determined that the second identification information is not associated (S7:N), the associated server 20 communicates with each of the payment server 10 and the payment terminal 40 to execute the payment using the first payment means (S8), and the process ends. The process of S8 is the same as the conventional method of executing the payment using only the first payment means.

If it is determined in S7 that the second identification information is associated (S7: Y), the cooperating server 20 determines whether or not to use the second payment means based on the use necessity setting associated with the first identification information included in the payment request (S9). If it is determined that the second payment means is not to be used (S9: N), the process proceeds to S8 and ends. If it is determined in S9 that the second payment means is to be used (S9: Y), the cooperating server 20 executes a process of acquiring the balance of the first payment means and the balance of the second payment means between the payment server 10 and the cooperating server 20 (S10). Note that the cooperating server 20 may execute the subsequent process based on the balance of the first payment means written to the IC card C, without acquiring the balance of the first payment means from the payment server 10.

The associated server 20 refers to the preferred usage setting associated with the first identification information included in the payment request (S11). If the preferred usage setting indicates the first payment method (S11: first payment method), the associated server 20 determines whether the balance of the first payment method is sufficient based on the payment amount included in the payment request and the balance of the first payment method (S12). If it is determined that the balance of the first payment method is sufficient (S12: Y), the associated server 20 proceeds to processing of S8 and this processing ends.

If it is determined in S12 that the balance of the first payment means alone is insufficient (S12:N), the cooperating server 20 determines whether the sum of the balance of the first payment means and the balance of the second payment means is sufficient (S13). If it is determined in S13 that the total is insufficient (S13:N), the cooperating server 20 notifies the payment terminal 40 of an error due to insufficient balance (S14), and this process ends. If it is determined that the total is sufficient (S13:Y), the process moves to FIG. 9, and the cooperating server 20 executes a charge from the second payment means to the first payment means (S15). The charge amount in this charge is the shortfall in the balance of the first payment means. The process of S18 executed after S15 will be described later.

In S11, if the preferred usage setting indicates the second payment method (S11: second payment method), the process moves to FIG. 9, where the linked server 20 determines whether the balance of the second payment method is sufficient based on the payment amount included in the payment request and the balance of the second payment method (S16). If it is determined that the balance of the second payment method is sufficient (S16: Y), the process moves to S15. The charge amount in this case is the payment amount included in the payment request.

If it is determined in S16 that the balance in the second payment method alone is insufficient (S16:N), the linked server 20 determines whether the sum of the balance in the first payment method and the balance in the second payment method is sufficient (S17). If it is determined that the sum is sufficient (S17:Y), the process proceeds to S15. The charge amount in this case is the full amount of the balance in the second payment method. If it is determined in S16 that the sum is insufficient (S17:N), the process proceeds to S14 and ends.

The associated server 20 executes the payment based on the balance of the first payment means after the charge in S15 (S18). The associated server 20 sends a payment completion notification to the payment terminal 40 indicating that the payment has been completed (S19). When the payment terminal 40 receives the payment completion notification (S20), it uses the reader/writer 46 to write the latest balance and the first history data to the IC card C (S21), and the process ends.

The partner server 20 transmits the first execution data and the second execution data to the payment server 10 (S22). When the payment server 10 receives the first execution data and the second execution data (S23), it updates the balance of the first payment means based on the first execution data (S24). The payment server 10 updates the balance of the second payment means based on the second execution data (S25), and this process ends. The second history data is also saved in the flow of S22 to S25.

In the present embodiment, when the first identification information is read by a payment terminal 40 that does not support the second payment means, the payment system 1 executes a second process for using the second payment means identified by the second identification information associated with the first identification information. This increases user convenience because even if the payment terminal 40 does not support the second payment means, the second payment means can be used by associating the first identification information with the second identification information. Since the number of payment terminals 40 that can use the second payment means increases, the use of the second payment means can be promoted. There is also no need to modify the payment terminal 40 to make it compatible with the second payment means. For example, when the payment terminal 40 is placed in a store, there is no need to modify the payment terminal 40, thereby increasing the convenience of the store.

Furthermore, the payment system 1 executes the second process when the priority usage setting indicates the second payment means. This allows the user to set whether to preferentially use the first payment means or the second payment means, thereby improving user convenience. For example, for a user who has associated the first payment identification information and the second identification information, it is possible to prioritize the second payment means by default without setting the priority usage. This aspect is also included in the present disclosure. However, in this aspect, in order for the user to use the first payment means, the balance of the second payment means must be set to zero or the association between the first payment identification information and the second identification information must be released. In this regard, the user can change the priority usage setting to use the first payment means whenever they like, allowing for highly flexible payment.

Furthermore, the payment system 1 executes the first process when the preferred usage setting indicates the second payment means and the balance of the second payment means is insufficient. As a result, even if the balance of the second payment means is insufficient, an error due to insufficient balance can be avoided by using the first payment means in combination. For example, if a user wants to mainly use the second payment means and use the first payment means as an auxiliary, the shortfall in the balance of the second payment means can be made up with the auxiliary first payment means, thereby saving the trouble of charging the second payment means. The user does not have to worry about the balance of the second payment means.

Furthermore, the payment system 1 executes the second process when the preferred usage setting indicates the first payment means and the balance of the first payment means is insufficient. As a result, even if the balance of the first payment means is insufficient, an error due to insufficient balance can be avoided by using the second payment means in combination. For example, if a user wants to mainly use the first payment means and use the second payment means as an auxiliary, the shortfall in the balance of the first payment means can be made up with the auxiliary second payment means, thereby saving the trouble of recharging the first payment means. The user does not have to worry about the balance of the first payment means.

In addition, when the first identification information is read by the payment terminal 40, the charge is made to the first payment means using the second payment means. After the charge is made, the payment is made based on the first payment means. The second process of this embodiment is a process of reducing the amount of the charge from the balance of the second payment means. As a result, if a mechanism for charging from the second payment means to the first means is introduced, the second payment means can be used in a payment terminal 40 that does not support the second payment means, so the amount of modification of the entire payment system 1 can be reduced. For example, it is only necessary to introduce the above-mentioned charge mechanism in the linked server 20 without making modifications to each individual payment terminal 40, so the amount of modification of the entire payment system 1 can be reduced. As a payment terminal 40, the second payment means can be essentially used with just the existing mechanism for the first payment means.

Furthermore, when the first identification information is read by the payment terminal 40, the charge from the second payment means to the first payment means is executed by the linked system 2 linked to the payment system 1. The payment system 1 executes the second process based on the second execution data received from the linked system 2. This allows the processing to be distributed between the payment system 1 and the linked system 2, thereby reducing the processing load on the payment system 1. The processing load on the linked system 2 is also reduced. For example, if a payment takes a long time, the user may remove the IC card C from the reader/writer 46, increasing the possibility of an error; however, by distributing the processing, the payment can be completed quickly, making it easier to avoid errors.

In addition, the IC card C records first history data indicating that charging was performed using the second payment means. When charging is performed, the payment system 1 associates the second history data indicating that charging was performed using the second payment means with the first identification information and stores it in the first payment means database DB1. This allows the IC card C to understand why the balance of the first payment means temporarily increased by the first history data. For example, when the user is allowed to check the charge history by reading the IC card C with the user terminal 30, the first history data allows the user to understand that the second payment means was used instead of the first payment means. For example, the user can understand why the payment was completed even though the balance of the first payment means has not decreased. The first payment means database DB1 also stores second history data indicating the same content as the first history data, so that the payment service provider can also understand why the balance of the first payment means temporarily increased. For example, in order to determine whether or not an unauthorized charge has been performed, the history known on the IC card C side can be compared with the history known on the payment service provider side. By carrying out this type of verification, it is possible to confirm that the charges are not fraudulent.

Furthermore, the payment system 1 executes the second process when the IC card C storing the first identification information is read by the payment terminal 40. This allows the user to use the second payment means by a simple operation of holding the IC card C over the payment terminal 40, thereby improving user convenience. For example, if the second payment means is a type that displays a two-dimensional code on the user terminal 30, the second payment means can be used by a simple operation of holding the IC card C rather than a series of operations such as starting up the user terminal 30, unlocking it, starting a dedicated application, and displaying the two-dimensional code, thereby improving user convenience.

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

Figure 10 is a diagram showing an example of functions realized in the modified example. As shown in Figure 10, in the modified example, an auto-charge execution unit 108, a coupon processing execution unit 109, and a receipt processing execution unit 110 are realized. The auto-charge execution unit 108, the coupon processing execution unit 109, and the receipt processing execution unit 110 are realized by the control unit 11.

[5-1. Modification 1]
For example, in the embodiment, a case where the first identification information and the second identification information correspond one-to-one has been given as an example. That is, a case where one first payment means is linked to one second payment means has been given as an example. The first identification information and the second identification information may correspond many-to-one. That is, multiple first payment means may be linked to one second payment means. Note that the first identification information and the second identification information may correspond one-to-many or many-to-many. That is, one first payment means may be linked to multiple second payment means, or multiple first payment means may be linked to multiple second payment means. These aspects are also included in the scope of the present disclosure.

FIG. 11 is a diagram showing an example of the association database DB3 of the first modification. The association unit 101 of the first modification associates multiple pieces of first identification information with second identification information. For example, when a user has multiple IC cards C, the association unit 101 associates the first identification information stored in each of the multiple IC cards C with the second identification information. For example, when a user collectively manages the IC cards C of family members, the association unit 101 associates the first identification information stored in the user's IC card C with the first identification information and second identification information stored in the IC cards C of the family members.

In the first variant, it is possible to specify the use necessity setting and the priority use setting for each first identification information. For this reason, the association database DB3 stores the use necessity setting and the priority use setting for each first identification information. The use necessity setting and the priority use setting may be common to a plurality of first identification information. In this case, there is a many-to-one correspondence between the first identification information and the use necessity setting and the priority use setting. The flow of the use necessity setting and the priority use setting is as described in the embodiment. For example, a person who possesses IC card C (user or family member) performs the use necessity setting and the priority use setting according to a flow similar to that shown in FIG. 2.

The second process execution unit 106 of the first modification example is capable of executing the second process, regardless of which of the multiple first identification information is read by the payment terminal 40. Here, executable means that the second process is in a state in which it can be executed, regardless of which of the multiple first identification information associated with a certain second identification information is read by the payment terminal 40. For this reason, it is not necessary to execute the second process for all first identification information, and if the payment terminal 40 reads first identification information associated with a usage necessity setting indicating that the second payment method will not be used, the second process is not executed.

Note that this embodiment differs from the embodiment in that multiple first identification information are associated with the second identification information, but the flow for executing the second process is the same as the embodiment. In the first modification, when the associated server 20 receives a payment request from the payment terminal 40, the associated server 20 only needs to refer to the association database DB3 and determine whether the second identification information is associated with the first identification information included in the payment request. Furthermore, the associated server 20 only needs to refer to the association database DB3 and execute the payment based on the usage necessity setting and the priority usage setting associated with the first identification information included in the payment request. The second process execution unit 106 only needs to execute the second process based on the second execution data received from the associated server 20.

The payment system 1 of the first variant associates a plurality of first identification information with the second identification information. The payment system 1 can execute the second process regardless of which of the plurality of first identification information is read by the payment terminal. This allows a plurality of first payment means to be linked to the second payment means, thereby improving user convenience. For example, even if a user holds a plurality of IC cards C, the linked second payment means can be consolidated into one. For example, even if the user's family also holds an IC card C, the second payment means linked to the family's IC card C can be consolidated into one.

[5-2. Modification 2]
For example, as described in the first modification, when multiple first identification information and second identification information are associated with each other, a usage necessity setting regarding whether or not to use the second payment means can be set for each first identification information. The second process execution unit 106 executes the second process when the first identification information of the first payment means for which a usage necessity setting indicating that the second payment means is to be used is read by the payment terminal 40. Although it differs from the embodiment in that a usage necessity setting can be set for each first identification information, the payment flow itself based on the usage necessity setting is the same as the embodiment.

The payment system 1 of the second modification allows for a setting as to whether or not to use the second payment means for each piece of first identification information. The payment system 1 executes the second process when the payment terminal 40 reads the first identification information of the first payment means for which a setting indicating that the second payment means will be used has been set. This allows for a setting as to whether or not to use the second payment means for each piece of first identification information, allowing for more flexible payment execution and thus improving user convenience.

[5-3. Modification 3]
For example, when the sum of the balance of the first payment means and the balance of the second payment means is insufficient, an error due to insufficient balance may not occur, but an auto-charge may be executed to complete the payment. Auto-charge is a charge that is executed automatically without the user performing any operation for charging. Auto-charge is executed based on a predetermined payment means. Hereinafter, this payment means is referred to as the third payment means.

The payment system 1 of the third modification includes an auto-charge execution unit 108. When the sum of the balance of the first payment means and the balance of the second payment means is insufficient, the auto-charge execution unit 108 executes auto-charge for at least one of the first payment means and the second payment means based on the third payment means. In the third modification, a case is described in which a credit card corresponds to the third payment means, but the third payment means may be any payment means different from the first payment means and the second payment means, and is not limited to a credit card. For example, the third payment means may be any payment means other than the first payment means and the second payment means, such as electronic money, points, a debit card, an account (including a bank account), cryptocurrency, or a wallet.

The third identification information capable of identifying the third payment means is stored in the first payment means database DB1, the second payment means database DB2, the association database DB3, or another database. The third identification information is associated with at least one of the first identification information and the second identification information. In variant 3, the third identification information is a credit card number. The third identification information may include other information such as the expiration date or the account holder of the credit card. If the third payment means is a payment means other than a credit card, the third identification information may include information capable of identifying the other payment means. This information itself may be publicly known information.

For example, the cooperating server 20 sends an auto-charge request to the payment server 10 when the sum of the balance of the first payment means and the balance of the second payment means is insufficient. The auto-charge request is data in a predetermined format for requesting the execution of auto-charge. For example, the auto-charge request includes at least one of the first identification information, the second identification information, and the third identification information. The auto-charge request may also include other information such as the auto-charge amount. When the payment server 10 receives the auto-charge request, the auto-charge execution unit 108 executes auto-charge based on the auto-charge request.

The auto-charge itself can use known processing. For example, the user may specify the auto-charge settings in advance, or default auto-charge settings prepared by the payment service may be used. The auto-charge settings are at least one of the balance of the first payment method that triggers auto-charge, the balance of the second payment method that triggers auto-charge, the auto-charge amount, and the third payment method used for auto-charge.

The auto-charge setting itself may be any setting, such as an auto-charge setting such as "when the balance is insufficient, charge a specified amount", an auto-charge setting such as "when the balance is insufficient, charge the shortfall", or an auto-charge setting such as "when the balance is insufficient, charge so that the balance of at least one of the first payment means and the second payment means after payment will be a specified amount". The auto-charge setting is stored in the first payment means database DB1, the second payment means database DB2, the association database DB3, or another database in association with at least one of the first identification information, the second identification information, and the third identification information.

For example, the auto-charge execution unit 108 may first execute auto-charge to the second payment means. After that, the auto-charge execution unit 108 may execute auto-charge to the first payment means based on the balance of the auto-charged second payment means. The auto-charge execution unit 108 may also directly auto-charge the first payment means, rather than relaying through the second payment means. Auto-charge may also be executed using multiple third payment means in combination.

Note that auto-charge may be executed by the associated server 20 instead of the payment server 10. In this case, the associated server 20 has the same functions as the auto-charge execution unit 108. Requesting auto-charge from the associated server 20 may correspond to the execution of auto-charge by the auto-charge execution unit 108 of the payment server 10. The payment server 10 obtains data indicating the execution result of auto-charge from the associated server 20. The payment flow after auto-charge is executed may be the same as in the embodiment.

In the payment system 1 of the third modification, when the sum of the balance of the first payment means and the balance of the second payment means is insufficient, an auto-charge is performed for at least one of the first payment means and the second payment means based on the third payment means. This makes it easier to avoid errors due to insufficient balances.

[5-4. Modification 4]
For example, when payment is completed, the auto-charge execution unit 108 may execute auto-charge for at least one of the first payment means and the second payment means. In the fourth modification, the user is assumed to specify the auto-charge setting in advance. In the fourth modification, a case will be described in which auto-charge using the third payment means described in the third modification can also be used, but auto-charge using only either the first payment means or the second payment means may be executed without using the third payment means.

The auto-charge setting in variant 4, like variant 3, may be any setting. For example, the auto-charge setting may be "when the balance falls below a threshold, charge a specified amount," or "when the balance falls below a threshold, charge so that the balance reaches a specified amount." The threshold and specified amount in these examples may be set to any value by the user.

Figure 12 is a diagram showing an example of auto-charge in variant 4. In the example of Figure 12, it is assumed that an auto-charge setting has been specified such as "execute auto-charge so that the balance of the first payment method after payment is 3,000 yen." Furthermore, it is assumed that the auto-charge setting was made after the balance reached the state shown in the upper part of Figure 12 (balance of the first payment method "AAA Money": 600 yen, balance of the second payment method "BBB Cash": 3,000 yen). The user can make the auto-charge setting from any screen displayed on the user terminal 30.

In the example of FIG. 12, the conditions of the payment amount, the balance of the first payment means before the payment, and the balance of the second payment means before the payment are the same as those in FIG. 3. For example, the auto-charge execution unit 108 determines whether the balance of the first payment means after the payment is less than 3000 yen. If the auto-charge execution unit 108 determines that the balance of the first payment means after the payment is 3000 yen or more, it does not execute auto-charge. If the auto-charge execution unit 108 determines that the balance of the first payment means after the payment is less than 3000 yen, it executes auto-charge so that the balance of the first payment means becomes 3000 yen. The charge amount is the numerical value obtained by subtracting the balance immediately after the payment from 3000 yen. Note that the numerical value included in the auto-charge setting may be any numerical value and is not limited to 3000 yen.

In the example of FIG. 12, if the usage necessity setting indicates that the second payment method is not to be used (branch "Do not use BBB Cash"), the first payment method alone is not sufficient, and an error occurs due to insufficient balance. In this case, instead of causing an error, auto-charge to the first payment method may be performed as in variant example 3. If the priority usage setting indicates the first payment method (branch "Use BBB Cash (AAA Money Prioritized)"), the auto-charge execution unit 108 uses the balance of the second payment method to perform auto-charge so that the balance of the first payment method becomes 3,000 yen.

For example, if there is a sufficient balance in the second payment means, it is possible to perform an auto-charge so that the balance in the first payment means becomes 3,000 yen, without using the third payment means. In the example of FIG. 12, the balance in the second payment means is not enough, so the auto-charge execution unit 108 also performs an auto-charge using the third payment means. For example, the auto-charge execution unit 108 uses a credit card, which is an example of the third payment means, to charge the shortfall of 400 yen. The flow of auto-charge when the preferred usage setting indicates the second payment means (branch of "Use BBB Cash (BBB Cash Priority)") is similar.

In the example of FIG. 12, a case where auto-charge of the first payment means is executed is described, but the auto-charge execution unit 108 may also execute auto-charge of the second payment means. For example, an auto-charge setting such as "execute auto-charge so that the balance of the second payment means after payment is 2000 yen" may be specified. The auto-charge execution unit 108 may execute both auto-charge of the first payment means and auto-charge of the second payment means. In the fourth variant example, the auto-charge execution unit 108 may also execute auto-charge of the first payment means through the second payment means.

In the payment system 1 of the fourth variant example, when a payment is completed, an auto-charge is performed for at least one of the first payment means and the second payment means. This makes it less likely that at least one of the first payment means and the second payment means will have insufficient balance in the next and subsequent payments. This saves the user the trouble of having to manually charge the account.

[5-5. Modification 5]
For example, as described in Modifications 3 and 4, the auto-charge execution unit 108 may execute auto-charge for the first payment means using the second payment means when the balance of the first payment means is less than the threshold value. When the balance of the second payment means is sufficient, the auto-charge execution unit 108 executes auto-charge using only the second payment means. When the balance of the second payment means is not sufficient, the auto-charge execution unit 108 may execute auto-charge using both the second and third payment means, or may execute auto-charge with the full amount of the second payment means without using the third payment means. The auto-charge settings may be the same as those in Modifications 3 and 4.

In the payment system 1 of the fifth variant, when the balance of the first payment means is below a threshold, the second payment means is used to perform an auto-charge for the first payment means. This makes it less likely that the first payment means will have an insufficient balance. This saves the user the trouble of having to manually charge the first payment means. For example, there are terminals that do not communicate every time a payment is made, but rather communicate when some operation is performed. Even if a payment is made using such a terminal after the payment described in the embodiment is made, a certain amount of balance can be secured, making it less likely that the balance will be insufficient.

[5-6. Modification 6]
For example, a coupon may be associated with at least one of the first identification information and the second identification information. A coupon is a benefit for a user. For example, a coupon may be a benefit that allows a product to be purchased or a service to be used at a discounted price or for free. A coupon may be a benefit that increases points awarded by payment. A coupon may be usable only at a specific member store, a specific product, or a specific service, or may be usable at all member stores, a specific product, or a specific service. For example, a coupon may be a first or second payment means that is usable only at a specific member store, a specific product, or a specific service. In the sixth variation, a case will be described in which a coupon owned by a user is automatically applied without the user presenting the coupon at a store.

In variant 6, an example is given of a case where a coupon is associated with the second identification information. In variant 6, coupon information is associated with the second identification information in the second payment means database DB2. The coupon information may be associated with the first identification information in the first payment means database DB1, or with the first identification information and the second identification information in the association database DB3. In other databases, the coupon may be associated with the first identification information and the second identification information.

Coupon information is information about the contents of the coupon. For example, coupon information is the discount rate, the discounted price, the applicable product or service, the stores where the coupon can be used, the validity period, other terms of use, or a combination of these. When a user acquires a coupon, the coupon information is associated with at least one of the user's first identification information and second identification information. The process itself that is executed when the coupon is acquired can be a publicly known process.

The payment system 1 of the sixth modified example includes a coupon processing execution unit 109. When the first identification information is read by the payment terminal 40, the coupon processing execution unit 109 executes coupon processing to use the coupon without presenting the coupon associated with at least one of the first identification information and the second identification information. Presenting the coupon means causing the display unit 35 of the user terminal 30 to display the coupon. For example, displaying a barcode or two-dimensional code for using the coupon corresponds to presenting the coupon. Presenting the coupon paper may also correspond to presenting the coupon.

The coupon processing itself may be a known process. For example, a process of reducing the price of a product or service, a process of providing a product or service free of charge, or a process of increasing points awarded for a payment corresponds to coupon processing. For example, when a payment is executed, the coupon processing execution unit 109 refers to coupon information associated with at least one of the first identification information and the second identification information. If the coupon information includes a usage condition, the coupon processing execution unit 109 determines whether the usage condition is satisfied.

For example, the coupon processing execution unit 109 determines whether the usage conditions are met by determining whether the coupon is within its usage period, whether the store, product, or service is covered by the coupon, or whether the payment amount is equal to or exceeds a threshold. The coupon processing execution unit 109 may execute coupon processing so that all coupons that satisfy the usage conditions are applied, or may execute coupon processing so that only some of the coupons that satisfy the usage conditions are applied.

For example, when first identification information is read by the payment terminal 40, the coupon processing execution unit 109 acquires at least one of the first identification information and the second identification information associated with the first identification information from the associated server 20. The coupon processing execution unit 109 executes the series of processes described above based on the coupon information associated with at least one of the first identification information and the second identification information. The coupon processing execution unit 109 transmits the coupon information to be used to the associated server 20.

For example, the associated server 20 executes a process of applying a coupon based on the coupon information received from the payment server 10. For example, the associated server 20 executes a process of deducting the payment amount. Note that in the sixth variant example, a case where a coupon is automatically applied has been described, but the user may be allowed to specify whether or not a coupon is automatically applied. Furthermore, the user may be allowed to specify the conditions for a coupon to be automatically applied.

In the payment system 1 of the sixth variant example, when the first identification information is read by the payment terminal, the payment system 1 executes a coupon process to use the coupon without presenting the coupon associated with at least one of the first identification information and the second identification information. This increases user convenience because the coupon is automatically applied without the user presenting the coupon.

[5-7. Modification 7]
For example, when a coupon is automatically applied as in the sixth modification, the user may not notice that the coupon has been applied. For this reason, a receipt indicating that the coupon has been applied may be output. The receipt may be output on receipt paper, but in the seventh modification, an electronic receipt, which is an electronic receipt, is output. For this reason, displaying the electronic receipt corresponds to outputting the receipt. The electronic receipt may have the same layout as a paper receipt, or may have a different layout from that of a paper receipt. The electronic receipt also includes a screen that displays the usage history of at least one of the first payment means and the second payment means.

The payment system 1 of the seventh variant includes a receipt processing execution unit 110. When coupon processing is executed, the receipt processing execution unit 110 executes receipt processing for outputting a receipt including coupon identification information that can identify a coupon that was used without presentation. The receipt processing is processing for displaying an electronic receipt on the user terminal 30. For example, sending display data of the screen of the electronic receipt to the user terminal 30 corresponds to the receipt processing.

In the seventh variation, the usage history information of at least one of the first and second payment means includes coupon information of automatically used coupons. When a user performs an operation to display an electronic receipt from the user terminal 30, the receipt processing execution unit 110 identifies the content of the automatically used coupon based on the target usage history information. The receipt processing execution unit 110 generates display data for an electronic receipt including the identified coupon content and sends it to the user terminal 30. Note that if some modifications are made to the payment terminal 40, the information of the automatically used coupon may be printed on a paper receipt instead of an electronic receipt.

When coupon processing is executed, the payment system 1 of variant 7 executes receipt processing to output a receipt including coupon identification information that can identify a coupon that was used without presentation. This makes it easier for the user to notice that the coupon was automatically applied. For example, it makes it easier to convey to the user how convenient the payment system 1 is.

[5-8. Modification 8]
For example, the present disclosure includes configurations that do not assume the configuration for executing processing according to charge information described in the embodiment among the configurations described in the embodiment and modified examples 1 to 7. Modified example 8 describes a configuration that does not assume this configuration. For example, in the embodiment, a payment terminal 40 that does not support the second payment means is described, but the payment terminal 40 may support the second payment means. The user may use the second payment means by using an information storage medium in which the first identification information is stored instead of the second identification information.

For example, suppose the first payment method is a type that uses the IC card C described in the embodiment. Suppose the second payment method is a type that requires a two-dimensional code to be displayed on the display unit 35. In this case, the payment terminal 40 that is compatible with both the first and second payment methods has a function of reading the IC card C with the reader/writer 46 and a function of reading the two-dimensional code with a camera or code reader.

In the above example, when a user wishes to use the second payment means, in the conventional method, the user needs to start up the user terminal 30 such as a smartphone, unlock the user terminal 30, start up the application for the second payment means, and have the two-dimensional code displayed on the display unit 35. In this regard, if the second payment means can be used with IC card C, the user will no longer need to perform this series of operations, which increases user convenience.

When the first identification information is read by a payment terminal 40 that supports both the first and second payment means, the flow of executing the second process for using the second payment means may be the same as that of the embodiment. A payment system 1 that makes a payment using a payment terminal 40 that supports both the first and second payment means is also included in the scope of this disclosure.

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

For example, the first payment means and the second payment means may be any combination. For example, the first payment means may be IC card-type electronic money, and the second payment means may be points. The first payment means may be points, and the second payment means may be online-type electronic money. The first payment means and the second payment means may be linked from the beginning, without the user having to set it. For example, the first payment means and the second payment means may be linked as a default setting.

For example, the functions described as being realized by the payment server 10 may be shared among multiple computers. The functions described as being realized by the payment server 10 may be realized by at least one of the associated server 20, the user terminal 30, and the payment terminal 40. The functions described as being realized by the associated server 20 may be realized by at least one of the payment server 10, the user terminal 30, and the payment terminal 40. The functions described above may be realized by at least one computer in the payment system 1.

[6. Notes]
For example, the payment system according to the present disclosure can be configured as follows.
(1)
an association unit that associates first identification information capable of identifying a first payment means with second identification information capable of identifying a second payment means;
a second processing execution unit that, when an IC chip storing the first identification information is read by a payment terminal that is not compatible with the second payment means, executes a second processing to use the second payment means identified by the second identification information associated with the first identification information;
Payment systems including.
(2)
The payment system further includes a priority usage setting unit that sets a priority usage setting for one of the first payment means and the second payment means to be used preferentially,
the second process execution unit executes the second process when the preferential use setting indicates the second payment method.
A payment system as described in (1).
(3)
the payment system further includes a first process execution unit that executes a first process for using the first payment means when the preferential use setting indicates the second payment means and the balance of the second payment means is insufficient;
A payment system as described in (2).
(4)
the second process execution unit executes the second process when the preferential usage setting indicates the first payment means and the balance of the first payment means is insufficient.
A payment system according to (2) or (3).
(5)
When the first identification information is read by the payment terminal, charging is performed on the first payment means using the second payment means, and payment is performed based on the first payment means after the charging is performed;
The second process is a process of deducting an amount corresponding to the charge from a balance of the second payment means.
A payment system according to any one of (1) to (4).
(6)
The charging is performed by a linked system linked to the payment system when the first identification information is read by the payment terminal,
The payment system further includes a receiving unit that receives second execution data related to an execution result of the charge from the linked system,
The second process execution unit executes the second process based on the second execution data.
A payment system as described in (5).
(7)
First history data indicating that the charge was performed using the second payment means is recorded in the IC chip,
the payment system further includes a storage unit configured to store, in a database, second history data indicating that the charge was made using the second payment means in association with the first identification information when the charge is made, the second history data.
A payment system according to (5) or (6).
(8)
The associating unit associates a plurality of pieces of first identification information with the second identification information;
the second process execution unit is capable of executing the second process regardless of which of the plurality of first identification information is read by the payment terminal.
A payment system according to any one of (1) to (7).
(9)
A setting as to whether or not to use the second payment means can be made for each of the first identification information,
The second process execution unit executes the second process when the first identification information of the first payment means for which the use necessity setting indicating that the second payment means is to be used is read by the payment terminal.
A payment system as described in (8).
(10)
the payment system further includes an auto-charge execution unit that executes auto-charge for at least one of the first payment means and the second payment means based on a third payment means when a sum of a balance of the first payment means and a balance of the second payment means is insufficient;
A payment system according to any one of (1) to (9).
(11)
The payment system further includes an auto-charge execution unit that executes auto-charge for at least one of the first payment means and the second payment means when payment is completed.
A payment system according to any one of (1) to (10).
(12)
the auto-charge execution unit executes auto-charge for the first payment means using the second payment means when the balance of the first payment means is less than a threshold value;
A payment system as described in (11).
(13)
The payment system further includes a coupon processing execution unit that, when the first identification information is read by the payment terminal, executes a coupon processing for using a coupon associated with at least one of the first identification information and the second identification information without presenting the coupon.
A payment system according to any one of (1) to (12).
(14)
The payment system further includes a receipt processing execution unit that executes a receipt process for outputting a receipt including coupon identification information that can identify the coupon used without presentation when the coupon processing is executed.
A payment system as described in (13).
(15)
the second process execution unit executes the second process when an IC card including the IC chip is read by the payment terminal.
A payment system according to any one of (1) to (14).

1 Payment system, 2 Linked system, N Network, 10 Payment server, 11, 21, 31, 41 Control unit, 12, 22, 32, 42 Memory unit, 13, 23, 33, 43 Communication unit, 20 Linked server, 30 User terminal, 34, 44 Operation unit, 35, 45 Display unit, 40 Payment terminal, 46 Reader/writer, C IC card, 100 Data memory unit, 101 Association unit, 102 Use necessity setting unit, 103 Priority use setting unit, 104 Reception unit, 105 First processing execution unit, 106 Second processing execution unit, 107 Storage unit, 108 Auto charge execution unit, 109 Coupon processing execution unit, 110 Receipt processing execution unit, 200 Data memory unit, 201 Payment request reception unit, 202 Payment execution unit, 300 Data memory unit, 301 Display control unit, 302 operation reception unit, 400 data storage unit, 401 acquisition unit, 402 payment request transmission unit, B10, B12, B14, B15, B16 buttons, M11, M13 modal, SC1 home screen, DB1 first payment method database, DB2 second payment method database, DB3 association database.

Claims (17)

an association unit that associates first identification information capable of identifying the first payment method and second identification information capable of identifying the online second payment method with a database of a server ;
a payment request receiving unit that, when an IC chip that stores the first identification information and does not store the second identification information is read by a payment terminal that is not compatible with the second payment means , receives a payment request including the first identification information from the payment terminal;
a second processing execution unit that executes a second processing to reduce a balance of the second payment means identified by the second identification information associated in the database with the first identification information included in the payment request ;
Payment systems including. The payment system further includes a priority usage setting unit that sets a priority usage setting for one of the first payment means and the second payment means to be used preferentially,
the second process execution unit executes the second process when the preferential use setting indicates the second payment method.
The payment system according to claim 1 . the payment system further includes a first process execution unit that executes a first process to reduce a balance of the first payment means when the preferential usage setting indicates the second payment means and a balance of the second payment means is insufficient;
The payment system according to claim 2. the second process execution unit executes the second process when the preferential usage setting indicates the first payment means and the balance of the first payment means is insufficient.
4. A payment system according to claim 2 or 3. When the first identification information is read by the payment terminal, a charge is made to the first payment means using the second payment means, and a payment is made based on the first payment means after the charge is made;
The second process is a process of deducting an amount corresponding to the charge from a balance of the second payment means.
A payment system according to any one of claims 1 to 3. The charging is performed by a linked system linked to the payment system when the first identification information is read by the payment terminal,
The payment system further includes a receiving unit that receives second execution data related to an execution result of the charge from the linked system,
The second process execution unit executes the second process based on the second execution data.
The payment system according to claim 5. First history data indicating that the charge was performed using the second payment means is recorded in the IC chip,
the payment system further includes a storage unit configured to store, in a database, second history data indicating that the charge was made using the second payment means in association with the first identification information when the charge is made, the second history data.
The payment system according to claim 5. The associating unit associates the first identification information and the second identification information of each of the plurality of first payment means ;
the second process execution unit is capable of executing the second process regardless of which of the plurality of first identification information is read by the payment terminal.
A payment system according to any one of claims 1 to 3. A setting as to whether or not to use the second payment means can be made for each of the first identification information,
The second process execution unit executes the second process when the first identification information of the first payment means for which the use necessity setting indicating that the second payment means is to be used is read by the payment terminal.
The payment system according to claim 8. the payment system further includes an auto-charge execution unit that executes auto-charge for at least one of the first payment means and the second payment means based on a third payment means when a sum of a balance of the first payment means and a balance of the second payment means is insufficient;
A payment system according to any one of claims 1 to 3. The payment system further includes an auto-charge execution unit that executes auto-charge for at least one of the first payment means and the second payment means when payment is completed.
A payment system according to any one of claims 1 to 3. the auto-charge execution unit executes auto-charge for the first payment means using the second payment means when the balance of the first payment means is less than a threshold value;
The payment system according to claim 11. The payment system further includes a coupon processing execution unit that, when the first identification information is read by the payment terminal, executes a coupon processing for using a coupon associated with at least one of the first identification information and the second identification information without presenting the coupon.
A payment system according to any one of claims 1 to 3. The payment system further includes a receipt processing execution unit that executes a receipt process for outputting a receipt including coupon identification information that can identify the coupon used without presentation when the coupon processing is executed.
The payment system according to claim 13. the second process execution unit executes the second process when an IC card including the IC chip is read by the payment terminal.
A payment system according to any one of claims 1 to 3. an associating step of associating first identification information capable of identifying the first payment means and second identification information capable of identifying the online second payment means in a database of a server ;
a payment request receiving step of receiving a payment request including the first identification information from a payment terminal when an IC chip that stores the first identification information and does not store the second identification information is read by a payment terminal that is not compatible with the second payment means;
a second processing execution step of executing a second processing step of deducting a balance of the second payment means identified by the second identification information associated in the database with the first identification information included in the payment request ;
A method for performing a process comprising the steps of: an association unit that associates first identification information capable of identifying the first payment means and second identification information capable of identifying the online second payment means with a database of the server ;
a second processing execution unit that, when an IC chip that stores the first identification information and does not store the second identification information is read by a payment terminal that is not compatible with the second payment means, executes a second processing to reduce a balance of the second payment means identified by the second identification information associated in the database with the first identification information included in a payment request that includes the first identification information received from the payment terminal;
A program that makes a computer function as a

Images