JP7645940B2 - Payment system, payment method, and program - Google Patents

Description

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

Conventionally, there are known technologies for promoting a cashless society using various payment methods (e.g., credit cards, points, or electronic money). For example, Patent Document 1 describes an information providing device that identifies payment methods available at a facility visited by a user and provides information to the user by displaying information on the identified payment methods on the user's terminal. Patent Document 2 describes a payment system that determines whether the payee on a payment slip read by a user's terminal supports a specific payment method.

JP 2016-062376 A JP 2022-011709 A

In the above-mentioned technologies, the use of certain payment methods may be prohibited at payment facilities where payments are made using a user terminal. For this reason, the system is required to determine whether a payment facility is a prohibited facility where the use of the payment source payment method set as the payment source in the user terminal is prohibited. However, the technologies in Patent Documents 1 and 2 cannot determine whether a payment facility is a prohibited facility.

One of the purposes of this disclosure is to determine whether a payment facility is a prohibited facility. However, the purpose of this disclosure is not limited to this purpose.

The payment system according to the present disclosure includes a payment facility information acquisition unit that acquires payment facility information related to a payment facility where a payment is made using a user terminal, an identification unit that identifies a payment source payment means set as the payment source of the payment, a facility determination unit that determines whether the payment facility is a prohibited facility where the use of the payment source payment means is prohibited based on the payment facility information, and a processing execution unit that executes a predetermined process when the facility determination unit determines that the payment facility is the prohibited facility.

According to this disclosure, it is possible to determine whether a payment facility is a prohibited facility.

FIG. 2 is a diagram illustrating an example of a hardware configuration of a payment system. FIG. 13 is a diagram illustrating an example of a screen displayed on a user terminal. FIG. 2 is a diagram showing an example of functions realized in the payment system. FIG. 4 is a diagram illustrating an example of a user database. FIG. 2 is a diagram illustrating an example of a facility database. 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 functions in a modified example. FIG. 13 is a diagram showing an example of a payment application screen in Modification 1. FIG. 23 is a diagram showing an example of a payment application screen in Modification Example 6. FIG. 23 is a diagram showing an example of a payment application screen in Modification Example 7. FIG. 2 is a diagram illustrating an example of a product database. A figure showing an example of a function realized in the payment system of variant example 9.

[1. Hardware configuration of the payment system]
An example of an embodiment of a payment system, a payment method, and a program according to the present disclosure will be described. FIG. 1 is a diagram showing an example of a hardware configuration of a payment system. For example, a payment system 1 is connected to a network N such as the Internet or a LAN. A user terminal 20 and a facility terminal 30 are also connected to the network N. Any computer can be connected to the network N. The computer connected to the network N is not limited to the example of FIG. 1.

For example, the payment system 1 includes a payment server 10. The payment server 10 is a server computer managed by a service provider that provides payment services to users. For example, the payment server 10 includes a control unit 11, a memory unit 12, and a communication unit 13. The control unit 11 includes at least one processor. The memory unit 12 includes at least one of 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 program stored in the storage unit 12 may be supplied to the payment server 10 via the network N. Also, the program stored in a computer-readable information storage medium may be supplied to the payment server 10 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, the payment system 1 may include at least one computer. The computers included in the payment system 1 are not limited to the example in FIG. 1. For example, the payment system 1 may include a payment server 10 and another server computer. The payment system 1 may include another computer other than the server computer, such as a personal computer, a tablet, or a smartphone. The payment system 1 may not include a server computer, and may only include another computer other than the server computer. The payment system 1 may include at least one of a user terminal 20 and a facility terminal 30.

The user terminal 20 is a user's computer. For example, the user terminal 20 is a smartphone, a tablet, a wearable terminal, or a personal computer. Although only one user terminal 20 is shown in FIG. 1, there may be a user terminal 20 for each of multiple users. One user may use multiple user terminals 20. For example, the user terminal 20 includes a control unit 21, a storage unit 22, a communication unit 23, an operation unit 24, a display unit 25, and an image capture unit 26.

For example, the hardware configurations of the control unit 21, the memory unit 22, and the communication unit 23 may be similar to those of the control unit 11, the memory unit 12, and the communication unit 13, respectively. The communication unit 23 may be capable of communicating with an IC chip, an IC card, or other media by NFC (Near Field Communication). The operation unit 24 is an input device such as a keyboard, a mouse, or a touch panel. The display unit 25 is a display such as a liquid crystal or organic EL. The photographing unit 26 includes at least one camera. The user terminal 20 may include an IC chip used for payment. The program stored in the memory unit 22 may be provided to the user terminal 20 via the network N or an information storage medium.

The facility terminal 30 is a computer of a facility that is an affiliated store of the payment service. The facility terminal 30 is sometimes called a payment terminal. For example, the facility terminal 30 is a POS terminal, a handheld terminal, a personal computer, a smartphone, a tablet, or a wearable terminal. Although only one facility terminal 30 is shown in FIG. 1, there may be a facility terminal 30 in each of multiple facilities. Multiple facility terminals 30 may be located in one facility. For example, the facility terminal 30 includes a control unit 31, a memory unit 32, a communication unit 33, an operation unit 34, a display unit 35, and an image capture unit 36.

For example, the hardware configurations of the control unit 31, memory unit 32, communication unit 33, operation unit 34, display unit 35, and image capture unit 36 may be similar to those of the control unit 11, memory unit 12, communication unit 13, operation unit 24, display unit 25, and image capture unit 26, respectively. The communication unit 33 may be capable of communicating with an IC chip, IC card, or other medium via NFC. The facility terminal 30 may include a code reader, reader/writer, IC card reader, magnetic card reader, or other reading device. The program stored in the memory unit 32 may be provided to the facility terminal 30 via the network N or an information storage medium.

[2. Overview of the payment system]
In this embodiment, an example is taken of a case where a user uses a payment service based on a payment app installed on the user terminal 20. The payment app is an application of a service provider. The user can use the payment service from any medium. The medium for the user to use the payment service is not limited to the payment app. For example, the user may use the payment service from a browser on the user terminal 20, an IC chip on the user terminal 20, an IC card, a magnetic card, a part of the user's own body, or other medium.

For example, a user can use multiple payment methods for a payment service. The payment method itself may be any of a variety of known methods. For example, the payment method may be a credit card, electronic money, a prepaid payment method other than electronic money, points, a bank account, an account at a financial institution other than a bank, an account at a financial institution other than a financial institution, cryptocurrency, a debit card, a wallet, or other methods. A code such as a barcode or a two-dimensional code is also a payment method in the sense that it is a method used for payment. For example, when a payment app is launched on the user terminal 20, a payment app screen for the user to use the payment service is displayed on the display unit 25.

FIG. 2 is a diagram showing an example of a screen displayed on the user terminal 20. For example, a code C10 is displayed on the payment application screen SC1. The code C10 may be of any type, for example, at least one of a barcode and a two-dimensional code. The code C10 may be only one of a barcode and a two-dimensional code. The code C10 is coded with an ID that can temporarily identify the user ("1234567890123456" in the example of FIG. 2). Hereinafter, the ID coded in the code C10 is referred to as a code ID. An expiration date may be set for the code ID. The code ID system may be a system used in known payment services.

For example, when the facility terminal 30 reads the code C10 with the photographing unit 36, payment is executed based on the payment method that is set in advance as the payment source from among multiple payment methods available to the user. In the example of FIG. 2, the user's credit card "Credit card C1" is set as the payment source. When the user selects button B11, at least one of the points ("AAA points" in FIG. 2) and electronic money ("AAA cash" in FIG. 2) held by the user is used in preference to the credit card set as the payment source.

For example, when the user selects button B12, the user can change the payment source to another payment method, such as another credit card, electronic money, or a bank account. When the user selects button B13, the user can configure a preferred usage setting, which is a setting for the payment method that is used preferentially when button B11 is selected. For example, the user specifies at least one of the type of payment method that is used preferentially and the upper limit of the payment amount for that payment method as the preferred usage setting.

For example, when the user selects button B14, the user can use a payment method in which a code is read by the photographing unit 26 of the user terminal 20. Hereinafter, this payment method is referred to as user-read payment. This payment method may also be called by other names. The general flow of user-read payment may be similar to a known flow. For example, in user-read payment, a code displayed on the display unit 35 of the facility terminal 30, or a code formed on a medium other than the facility terminal 30 (e.g., paper), is read by the photographing unit 26 of the user terminal 20. An example of the process executed when the user selects user-read payment will be described in Variation 6 below.

For example, when the user selects button B15, the user can use a type of payment method that can be completed simply by operating the user terminal 20. Hereinafter, this payment method is referred to as self-payment. This payment method may also be called by other names. The general flow of self-payment may be similar to a known flow. For example, in self-payment, the user selects a facility that is the subject of payment from a list of facilities near the user terminal 20. An example of the process that is executed when the user selects self-payment will be described in Variation 7 below.

In this embodiment, an example of processing will be described when a user selects a payment method in which the facility terminal 30 reads the code C10. Hereinafter, this payment method will be referred to as code payment. This payment method may also be called by other names. The general flow of code payment may be similar to known flows. For example, in code payment, when the facility terminal 30 reads the code C10 with the photographing unit 36, it transmits information such as the code ID extracted from the code C10 to the payment server 10. This information may be similar to known code payment information. The payment server 10 executes the code payment payment based on this information.

For example, laws, ordinances, government policies, or other circumstances may prevent a user from using a particular payment method to pay for a particular product. For example, a user cannot use a credit card to pay for ongoing lessons at a cram school (an example of a continuous service) and fees incurred at a customs inspection station. A user cannot use points to pay for medical expenses at a hospital or for medicine at a pharmacy. The use of particular payment methods may also be restricted for other payments.

In this embodiment, the payment server 10 manages each of the facilities affiliated with the payment service in association with information on the payment methods available at the facility. When the payment server 10 receives a payment request from a facility, it determines whether the payment method set as the payment source is available at the facility. If it is determined that the payment method is available at the facility, the payment is executed. In this case, for example, a window W16 indicating that the payment has been completed is displayed, as in the payment app screen SC1 in the upper right of Figure 2.

On the other hand, if it is determined that the payment method set as the payment source cannot be used at the facility, the payment is not executed. In this case, for example, as shown in the payment app screen SC1 in the lower right of Figure 2, a window W17 is displayed indicating that the payment method set as the payment source cannot be used at the facility. In the example of window W17 in Figure 2, a message is displayed to the user urging them to change the payment source.

For example, when window W17 is displayed on payment app screen SC1, the user closes window W17 and then selects button B12 to change the payment source. If the facility where the user is attempting to make payment prohibits the use of credit cards but allows electronic money, points, or bank accounts, the user changes the payment source to electronic money, points, or bank account. When the user performs the code payment operation again, the payment is completed. In this way, the payment system 1 of this embodiment is configured to determine whether or not the payment method set as the payment source can be used at the facility. Details of the payment system 1 will be explained below.

[3. Functions Realized by the Payment System]
Fig. 3 is a diagram showing an example of functions implemented in payment system 1. Fig. 3 also shows an example of functions implemented in each of user terminal 20 and facility terminal 30.

[3-1. Functions realized by the payment system]
For example, the payment server 10 includes a data storage unit 100, a payment facility information acquisition unit 101, a user identification information acquisition unit 102, an identification unit 103, a facility determination unit 104, a processing execution unit 105, and a payment execution unit 106. The data storage unit 100 is realized by the storage unit 12. The payment facility information acquisition unit 101, the user identification information acquisition unit 102, the identification unit 103, the facility determination unit 104, the processing execution unit 105, and the payment execution unit 106 are realized by the control unit 11.

[Data storage unit]
The data storage unit 100 stores data necessary for settlement. For example, the data storage unit 100 stores a user database DB1 and a facility database DB2.

Figure 4 is a diagram showing an example of user database DB1. User database DB1 is a database that stores various information related to each of multiple users. For example, user database DB1 stores user IDs, passwords, code IDs, payment source information, priority setting information, point information, electronic money information, payment method information, and history information. Any information related to users may be stored in user database DB1. The information stored in user database DB1 is not limited to the example in Figure 4. For example, the expiration date of a code ID may be stored in user database DB1.

The user ID is an example of user identification information that can identify a user. Therefore, any reference to a user ID can be read as user identification information. User identification information may be any information that can identify a user in some way. User identification information is not limited to a user ID. For example, user identification information may be an email address or a phone number. In this embodiment, the user ID and password are used by the user to log in to the payment service from the payment app.

For example, the payment server 10 issues a code ID for a user so that it does not overlap with the code IDs of other users. A code ID may be issued each time the payment app is launched. A code ID may be issued when a user performs a specified operation to update the code ID. When the payment server 10 issues a code ID for a user, it associates the code ID with the user ID of the user and stores the code ID in the user database DB1. The code ID corresponds to information that can identify a user, and is therefore an example of user identification information.

The payment source information is information about the payment means set as the payment source. Hereinafter, this payment means is referred to as the payment source payment means. The payment source payment means is the payment means selected by the user as the payment source from among multiple payment means available to the user. The user may select multiple payment source payment means. In this case, multiple payment source payment means may be used in combination, or multiple payment source payment means may be prioritized. In this embodiment, when a user selects button B12 to change the payment source payment means, the payment server 10 updates the payment source information associated with the user's user ID so that the payment source information indicates the changed payment source payment means.

The priority setting information is information regarding the setting of a payment method to be used in preference to the payment source payment method. Hereinafter, the payment method is referred to as the priority payment method. The priority payment method may be specified by the user, or may be fixed so that the user cannot specify it. In this embodiment, at least one of points and electronic money corresponds to the priority payment method. When a user selects button B13 to change the setting of the priority payment method, the payment server 10 updates the priority setting information associated with the user ID of the user so that the priority setting information indicates the changed setting. The priority setting information may include information indicating whether the user has selected button B11. The priority payment method may be any payment method and is not limited to points and electronic money. For example, the priority payment method may be a prepaid payment method other than electronic money, or a bank account.

Point information is information about points held by a user. For example, point information indicates the point balance, the breakdown of the balance, the point acquisition history, or other information. When a user acquires or uses points, the payment server 10 updates the point information associated with the user ID of that user. Point information may be stored in a database other than the user database DB1.

The electronic money information is information about electronic money held by a user. For example, the electronic money information indicates the electronic money balance, the breakdown of the balance, the electronic money recharge history, or other information. When a user recharges or uses electronic money, the payment server 10 updates the electronic money information associated with the user ID of the user. The electronic money information may be stored in a database other than the user database DB1.

Payment method information is information about a payment method that can be used by a user in a payment service. The payment method can also be said to be a payment method of the user registered in the payment service or payment app. The payment method can also be said to be a payment method that is a candidate for the payment source. In this embodiment, an example is given in which a user can use multiple payment methods, but the user may be able to use only one payment method. For example, when a user performs an operation to register information about his or her own payment method in a payment service, the payment server 10 updates the payment method information so that the payment method information associated with the user's user ID indicates the payment method.

For example, payment method information indicates at least a part of a credit card number, expiration date, account holder, or a combination of these. If a user registers multiple credit cards with a payment service or payment app, the payment method information indicates information such as the credit card numbers of each of the multiple credit cards. If a user registers a bank account with a payment service or payment app, the payment method information indicates the financial institution code, branch name, account type, account number, account holder, or a combination of these. If a user registers another payment method, such as cryptocurrency, with a payment service or payment app, the payment method information may indicate information about the other payment method.

The history information is information related to the usage history of the payment service. For example, the history information indicates the date and time of payment, the payment location (the facility where the payment was made), the payment amount, the payment method information of the payment method used in the payment, the points earned, or a combination of these. When the user uses the payment service, the payment server 10 updates the history information.

Figure 5 is a diagram showing an example of facility database DB2. Facility database DB2 is a database that stores various information related to each of a plurality of facilities. For example, facility ID, facility name, business type, and availability information are stored in facility database DB2. Any information related to the facility may be stored in facility database DB2. The information stored in facility database DB2 is not limited to the example in Figure 5. For example, the location of the facility and information on the products handled at the facility may be stored in facility database DB2.

The facility ID is an example of facility identification information that can identify a facility. Therefore, any place that says facility ID can be read as facility identification information. The facility identification information may be any information that can identify a facility in some way. The facility identification information is not limited to a facility ID. For example, the facility identification information may be an email address, a telephone number, or a facility name. The facility name and business type stored in the facility database DB2 may be specified by the facility or by the service provider.

The usability information is information regarding the usability of a payment method at a facility. The usability information indicates at least one of payment methods usable at the facility and payment methods prohibited for use at the facility. In the example of FIG. 5, the usability information indicates both of these, but the usability information may indicate only one of these. For example, the usability information may indicate only payment methods usable at a facility. In this case, payment methods not indicated in the usability information for a facility are prohibited for use at that facility. Conversely, the usability information may indicate only payment methods prohibited for use at a facility. In this case, payment methods not indicated in the usability information for a facility are usable at that facility.

In this embodiment, the usability information indicates whether four payment methods, namely credit cards, points, electronic money, and bank accounts, can be used. The usability information may indicate whether any payment method can be used. The payment methods indicated by the usability information are not limited to the example of this embodiment. For example, the usability information may indicate whether one, two, three, or five or more payment methods can be used. The usability information may indicate whether a prepaid payment method other than electronic money, an account at a financial institution other than a bank, an account other than a financial institution, cryptocurrency, a debit card, a wallet, or other payment method can be used.

For example, the availability information is specified by the service provider. The service provider specifies the availability information for a facility taking into consideration the type of business of the facility. For example, if a facility is a cram school, the service provider specifies the availability information for the facility so that the availability information indicates that the use of credit cards is prohibited and that other payment methods can be used, since there is a possibility that continuous service will be provided. If a facility is a hospital, the service provider specifies the availability information for the facility so that the availability information indicates that the use of points is prohibited and that other payment methods can be used, since there is a possibility that medical procedures will be performed.

The availability information may be automatically specified by the payment server 10 or another computer. In this case, it is assumed that the correspondence between each of the multiple industries and the availability information is predefined in the data storage unit 100. The payment server 10 or another computer specifies the availability information of a facility so that the availability information is associated with the industry of the facility. The availability information may be specified by a person in charge of the facility or by another person. Furthermore, availability information may not be prepared for each facility, but may be prepared for other units such as industry.

The data storage unit 100 can store any data. The data stored in the data storage unit 100 is not limited to the user database DB1 and the facility database DB2. For example, the data storage unit 100 may store the information described as being stored in each of the user database DB1 and the facility database DB2 in multiple databases. The data storage unit 100 may store data necessary for displaying the payment application screen SC1. The data storage unit 100 may store other data necessary for payment.

[Payment facility information acquisition unit]
The payment facility information acquisition unit 101 acquires payment facility information related to a payment facility where a payment is made using the user terminal 20. A payment facility can be a facility where a user makes a payment, a facility used by a user, a facility visited by a user, or a facility that receives a user's payment. A payment facility is not limited to immobile real estate, but may be mobile, such as a mobile store. In this embodiment, the facility where the facility terminal 30 that reads the code C10 is located corresponds to the payment facility.

The payment facility information is information capable of identifying at least one of the payment facility and the facility terminal 30. In this embodiment, an example is given in which the facility ID of the payment facility corresponds to the payment facility information. Therefore, the places where it is written "facility ID" can be read as "payment facility information." The payment facility information can be any information related to the payment facility, and is not limited to the facility ID. For example, the payment facility information can be the facility name, the account of the facility terminal 30, the terminal name of the facility terminal 30, the IP address of the facility terminal 30, or other information. In other words, the payment facility information can be facility terminal identification information capable of identifying the facility terminal 30. Note that since the facility terminal identification information can also identify the facility, the facility terminal identification information can also be considered a type of facility identification information.

In this embodiment, the payment facility information acquisition unit 101 acquires the facility ID of the payment facility from the facility terminal 30. For example, when the facility terminal 30 reads the code C10 with the photographing unit 36, it transmits a payment request including the code ID, facility ID, and payment amount (payment amount) extracted from the code C10 to the payment server 10. The payment request may also include other information. The payment facility information acquisition unit 101 acquires the facility ID included in the payment request received by the payment server 10. Note that the facility ID is not included in the payment request and may be data separate from the payment request.

[User Identification Information Acquisition Unit]
The user identification information acquisition unit 102 acquires user identification information from the facility terminal 30. In this embodiment, a code ID is an example of user identification information. The code ID is coded into a code C10. The user identification information acquisition unit 102 acquires a code ID included in a payment request as user identification information from the facility terminal 30. The code ID is not included in the payment request and may be data separate from the payment request. In the case where other user identification information such as a user ID is coded into a code C10, the user identification information acquisition unit 102 may acquire the other user identification information from the facility terminal 30. The user identification information acquisition unit 102 may acquire user identification information from a computer other than the facility terminal 30 (e.g., the user terminal 20).

In addition, when the code C10 is not used, the user identification information acquisition unit 102 may acquire user identification information that is not particularly coded from the facility terminal 30. For example, when the user identification information stored in the user terminal 20 is transmitted to the facility terminal 30 using wireless communication such as NFC communication, the user identification information acquisition unit 102 may acquire from the facility terminal 30 the user identification information acquired by the facility terminal 30 using wireless communication. In addition to wireless communication, the facility terminal 30 may acquire user identification information by voice uttered by the user terminal 20 or by manual input to the facility terminal 30.

[Specific part]
The identification unit 103 identifies the payment source payment means set as the payment source of the payment. For example, the identification unit 103 identifies the payment source payment means by referring to the payment source information stored in the user database DB1. In this embodiment, the identification unit 103 identifies the payment source payment means based on the code ID acquired from the facility terminal 30. For example, the identification unit 103 identifies the payment source payment means by referring to the payment source information associated with the code ID included in the payment request. In the example of FIG. 2, the payment source payment means is a credit card.

If the payment source information is stored in a database other than the user database DB1, the identification unit 103 may identify the payment source settlement means by referring to the other database. The payment source information may also be stored in the user terminal 20. If the facility terminal 30 is capable of acquiring the payment source information from the user terminal 20, the identification unit 103 may acquire the payment source information from the facility terminal 30 to identify the payment source settlement means. The identification unit 103 may acquire the payment source information from the user terminal 20 to identify the payment source settlement means.

[Facility Judgment Department]
The facility determination unit 104 determines whether the payment facility is a prohibited facility where the use of the payment source payment means is prohibited based on the facility ID. A prohibited facility can also be said to be a facility where the payment source payment means cannot be used. For example, the facility determination unit 104 determines whether the payment facility is a prohibited facility based on the facility database DB2. The facility determination unit 104 determines whether the payment facility is a prohibited facility based on the availability information associated with the facility ID included in the payment request and the payment source payment means identified by the identification unit 103.

For example, the facility determination unit 104 determines that a payment facility is a prohibited facility when the usability information indicates that use of the payment source payment means is prohibited. The facility determination unit 104 determines that a payment facility is a prohibited facility when the usability information indicates that the payment source payment means is not usable. For example, the facility determination unit 104 determines that a payment facility is not a prohibited facility when the usability information indicates that the payment source payment means is usable. The facility determination unit 104 determines that a payment facility is not a prohibited facility when the usability information indicates that use of the payment source payment means is not prohibited.

The facility determination unit 104 determining whether or not a payment facility is a prohibited facility has the same meaning as the facility determination unit 104 determining whether or not a payment facility is a permitted facility that is permitted to use the payment source payment means. When a payment facility is not a prohibited facility, it means that the payment facility is a permitted facility. When a payment facility is a prohibited facility, it means that the payment facility is not a permitted facility.

[Processing execution unit]
The processing execution unit 105 executes a predetermined processing when the facility determination unit 104 determines that the payment facility is a prohibited facility. The predetermined processing is processing that is executed or not executed depending on the determination result of the facility determination unit 104. In other words, the predetermined processing is processing that is executed on the condition that the payment facility is a prohibited facility. The processing execution unit 105 does not execute the predetermined processing when the facility determination unit 104 determines that the payment facility is not a prohibited facility.

For example, the process execution unit 105 executes a change process as a predetermined process to change the payment source to an available payment method available at the payment facility and execute the payment. An available payment method can also be a payment method whose use is not prohibited at a prohibited facility. In the example of the cram school in FIG. 5, the available payment method is electronic money. The available payment method may also be points or a bank account. In the example of the hospital in FIG. 5, the available payment method is a credit card, electronic money, or a bank account.

In this embodiment, an example is given of a case where prompting the user to change the payment source and execute the payment corresponds to the change process. In the example of Figure 2, the process for displaying window W17 corresponds to the change process. For example, when the facility determination unit 104 determines that the payment facility is a prohibited facility, the process execution unit 105 executes the change process by sending data showing window W17 to the user terminal 20. Based on the data, the user terminal 20 displays window W17 on the payment app screen SC1.

The change process is not limited to the example of this embodiment. For example, the change process may be a process for prompting the user to change the payment source using a medium other than window W17 (for example, an image other than window W17, a banner notification, a push notification, sound, or vibration). For example, the change process may be a process for prompting the user to change the payment source using a screen other than the payment app screen SC1.

For example, the change process may be a process for prompting the facility terminal 30, rather than the user terminal 20, to change the payment source. In this case, the change process causes a message or the like prompting the user to change the payment source to be displayed on the facility terminal 30. The user may change the payment source by visually checking the message or the like, or by a facility staff member conveying the contents of the message to the user.

For example, the change process may be a process of forcibly changing the payment source to an available payment method and making a payment. The user may be able to set whether or not to forcibly change the payment source. For example, if the user wishes to forcibly change the payment source, the user sets this in advance. If there is no user setting, the change process may be a process of prompting the user to change the payment source rather than a forcible change of the payment source. The change process may be a process of displaying on the user terminal 20 a screen that is displayed when the user selects button B12.

The predetermined process may be any process that is executed when the payment facility is determined to be a prohibited facility. The predetermined process is not limited to a change process. For example, the predetermined process may be a process for notifying at least one of the user terminal 20 and the facility terminal 30 that an error has occurred in the execution of the payment. The predetermined process may be a process for suspending the execution of the payment. The predetermined process may not prompt a change to an available payment method, but simply notify at least one of the user terminal 20 and the facility terminal 30 that the payment cannot be made using the source payment method.

[Payment Execution Department]
The payment execution unit 106 executes the payment. For example, when the facility determination unit 104 determines that the payment facility is not a prohibited facility, the payment execution unit 106 executes the payment based on the payment source payment means. When the facility determination unit 104 determines that the payment facility is a prohibited facility, the payment execution unit 106 does not execute the payment based on the payment source payment means. When the user changes the payment source to an available payment means, the payment execution unit 106 executes the payment based on the available payment means. The method of executing the payment itself may be the same as the method adopted in a known payment service. The payment execution unit 106 executes credit card payment, point payment, electronic money payment, bank account payment, or other payment. In this embodiment, the case where the payment system 1 includes the payment execution unit 106 will be described, but the payment may be executed in an external system linked to the payment system 1.

[3-2. Functions realized by user terminal]
The user terminal 20 includes a data storage unit 200, a display control unit 201, and an operation reception unit 202. The data storage unit 200 is realized by the storage unit 22. The display control unit 201 and the operation reception unit 202 are realized by the control unit 21.

[Data storage section]
The data storage unit 200 stores data necessary for the user to use the payment service. For example, the data storage unit 200 stores a payment application or a browser for displaying each screen such as the payment application screen SC1. In this embodiment, the data storage unit 200 stores the code ID that the user terminal 20 receives from the payment server 10.

[Display control unit]
The display control unit 201 displays each screen, such as a payment application screen SC1, on the display unit 25 based on the payment application or browser stored in the data storage unit 200. For example, the display control unit 201 displays a code C10 based on a code ID. It is assumed that a program for generating the code C10 is stored in the data storage unit 200.

[Operation reception section]
The operation reception unit 202 receives operations on various screens displayed by the display control unit 201. Data indicating the contents of the operations is transmitted to the payment server 10.

[3-3. Functions realized by facility terminals]
The facility terminal 30 includes a data storage unit 300, a user identification information acquisition unit 301, and a transmission unit 302. The data storage unit 300 is realized by the storage unit 32. The user identification information acquisition unit 301 and the transmission unit 302 are realized by the control unit 31.

[Data storage section]
The data storage unit 300 stores data necessary for a facility to use a payment service. For example, the data storage unit 300 stores a management tool for the facility. In this embodiment, the data storage unit 300 stores a facility ID.

[User Identification Information Acquisition Unit]
The user identification information acquisition unit 301 acquires user identification information from the user terminal 20. In this embodiment, a code ID corresponds to the user identification information. For example, the user identification information acquisition unit 301 acquires the code ID by reading a code C10 displayed on the user terminal 20 with the photographing unit 36. The user identification information acquisition unit 301 may acquire the code ID by using voice or communication instead of optically.

[Transmitter]
The transmitting unit 302 transmits information necessary for payment to the payment system 1. For example, the transmitting unit 302 transmits a payment request including a facility ID, a code ID, and a payment amount to the payment system 1. The payment request itself may be in a format used in known payment services. The payment request may include any information. Information described in this embodiment as being included in the payment request may be transmitted to the payment server 10 as data separate from the payment request.

[4. Processing Executed by the Payment System]
Fig. 6 is a diagram showing an example of a process executed in payment system 1. Fig. 6 also shows an example of a process executed in each of user terminal 20 and facility terminal 30. The process in Fig. 6 is executed by control units 11, 21, and 31 operating in accordance with programs stored in storage units 12, 22, and 32, respectively.

As shown in FIG. 6, when the payment app is launched, the user terminal 20 executes a login process between the user terminal 20 and the payment server 10 to allow the user to log in to the payment service (S1). In S1, the user terminal 20 transmits the user ID and password entered by the user to the payment server 10. The payment server 10 checks whether the user ID and password exist in the user database DB1. The login process may be executed by a known method.

When login is successful in S1, the user terminal 20 executes processing with the payment server 10 to display the payment application screen SC1 (S2). In S2, the payment server 10 generates a code ID and stores it in the user database DB1. The payment server 10 transmits the code ID to the user terminal 20. The user terminal 20 generates a code C10 based on the code ID and displays the payment application screen SC1 on the display unit 25. The processing when the facility terminal 30 reads the code C10 will be described below. It is assumed that the facility terminal 30 determines the payment amount based on at least one of reading the barcode of the product and input from the operation unit 34.

When the facility terminal 30 reads the code C10 with the photographing unit 36, it extracts the code ID from the code C10 (S3). The facility terminal 30 sends a payment request including the facility ID, code ID, and payment amount to the payment server 10 (S4). The payment server 10 receives the payment request from the facility terminal 30 (S5). The payment server 10 acquires the facility ID and code ID included in the payment request (S6). The payment server 10 refers to the user database DB1 and identifies the payment source payment means based on the payment source information associated with the code ID (S7).

The payment server 10 refers to the facility database DB2 and determines whether the payment facility is a prohibited facility based on the availability information associated with the facility ID and the source payment means identified in S7 (S8). If it is determined in S8 that the payment facility is not a prohibited facility (S8:N), the payment server 10 executes the payment based on the source payment means identified in S7 and the payment amount included in the payment request (S9), and the process ends. In this case, a window W16 indicating that the payment has been completed is displayed on the payment application screen SC1 of the user terminal 20. A notification indicating that the payment has been completed is displayed on the display unit 35 of the facility terminal 30.

If it is determined in S8 that the payment facility is a prohibited facility (S8: Y), the payment server 10 does not execute the payment, but sends a notification to the user terminal 20 prompting the user to change the payment source and execute the payment (S10). When the user terminal 20 receives the notification from the payment server 10 (S11), it displays a window W17 prompting the user to change the payment source on the payment application screen SC1 (S12), and the process ends. A notification indicating that the payment was not executed is displayed on the facility terminal 30. After the user changes the payment source, when the facility terminal 30 reads the code C10 with the photographing unit 36, the process from S3 onwards is executed again.

5. Summary of the embodiment
The payment system 1 of this embodiment acquires the facility ID of the payment facility where payment is made using the user terminal 20. The payment system 1 identifies the payment source payment means set as the payment source of the payment. The payment system 1 determines whether the payment facility is a prohibited facility based on the payment facility information. If it is determined that the payment facility is a prohibited facility, the payment system 1 executes a predetermined process. This allows the payment system 1 to determine whether the payment facility is a prohibited facility. The payment system 1 can execute a predetermined process based on the result of the determination of whether the payment facility is a prohibited facility.

For example, suppose that payment of tuition fees for lessons held continuously at a cram school (an example of continuous service provision) is prohibited from being made with a credit card. A cram school is a prohibited facility where the use of credit cards is prohibited. Therefore, if the payment system 1 prevents credit card payments from being made at a cram school as a specified process, it can prevent credit card payments from being made at the cram school.

When a payment other than tuition fees is made at a cram school (for example, a payment for stationery sold at the cram school), it is not a payment for tuition fees for ongoing classes, so payment can be made by credit card. However, payment system 1 may not be able to identify for what merchandise the payment is being made (for example, whether it is a payment for tuition fees for ongoing classes at the cram school, or a payment for stationery sold at the cram school). For this reason, payment system 1 can reliably prevent prohibited payment methods from being used by making a judgment on a payment facility basis.

In addition, the payment system 1 executes a change process as a predetermined process for changing the payment source to an available payment method available at the payment facility and executing the payment. This increases user convenience while preventing the use of prohibited payment methods. For example, if the change process notifies the user of what payment methods are available, the user can easily understand what the payment source needs to be changed to in order to complete the payment. For example, if the change process automatically changes the available payment method, the user does not need to perform an operation to change the payment source.

The payment source payment method is a credit card. The available payment method is electronic money. This allows the payment system 1 to change the payment source from a credit card to electronic money and execute the payment.

The user terminal 20 also displays the code C10 based on the code ID. The facility terminal 30 reads the code C10 to obtain the code ID. The facility terminal 30 transmits the facility ID and the code ID to the payment system 1. The payment system 1 obtains the facility ID and the code ID from the facility terminal 30. The payment system 1 identifies the payment source payment means based on the code ID. This allows the payment system 1 to determine whether or not the payment facility is a prohibited facility during the code payment. The payment system 1 can execute a specified process based on the result of the determination of whether or not the payment facility is a prohibited facility during the code payment.

[6. 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 7 is a diagram showing an example of functions in a modified example. As shown in Figure 7, the payment server 10 includes a history information acquisition unit 107, a necessity determination unit 108, a location information acquisition unit 109, a payment product information acquisition unit 110, and a product determination unit 111. Each of the history information acquisition unit 107, the necessity determination unit 108, the location information acquisition unit 109, the payment product information acquisition unit 110, and the product determination unit 111 is realized by the control unit 11.

[6-1. Modification 1]
For example, the specified processing executed by the processing execution unit 105 is not limited to the example of the embodiment. In variant 1, another example of the specified processing will be described. The available payment means in variant 1 is a payment means that can be recharged. The available payment means in variant 1 has a balance. Recharging means increasing the balance. Recharging can also be called depositing money. In variant 1, an example is taken in which the available payment means is electronic money. The available payment means may be any payment means that has a balance concept. For example, the available payment means may be a prepaid payment means other than electronic money, an account at a financial institution, an account other than a financial institution, cryptocurrency, a wallet, or other payment means.

Figure 8 is a diagram showing an example of the payment application screen SC1 in variant 1. The process execution unit 105 in variant 1 executes, as predetermined processes, a charge process for charging an available payment means based on the payment source payment means, and a change process. In the example of Figure 8, the process execution unit 105 executes, as the charge process, a process for displaying a window W18 indicating that the payment source payment means is a credit card, which is the payment source payment means, and a prompt to charge the available payment means, electronic money. The process execution unit 105 executes the charge process by transmitting data showing the window W18 to the user terminal 20. The change process is the same as in the embodiment. In the example of Figure 8, the process for displaying the window W17 corresponds to the change process.

The charge process may be any process related to charging the available payment means, and is not limited to displaying window W18. For example, it may be a process that uses a medium other than window W18 (e.g., an image other than window W18, a banner notification, a push notification, sound, or vibration) to encourage the user to charge the available payment means. The charge process may be a process that executes a forced charge (auto-charge) of the available payment means. In variant 1, the available payment means is charged by the amount specified by the user.

The method of charging the available payment means may be any of various known methods. The user may be able to set in advance whether or not to forcibly charge the available payment means. When the user sets the available payment means to indicate that he or she wishes to forcibly charge the available payment means, the process execution unit 105 executes the forcible charging of the available payment means as the charge process. When the user sets the available payment means to indicate that he or she does not wish to forcibly charge the available payment means, the process execution unit 105 executes the charge process by sending data showing window W18 in FIG. 8 to the user terminal 20.

The payment system 1 of the first variant executes a recharge process for recharging an available payment means based on the payment source payment means, and a change process as predetermined processes. This allows the payment system 1 to recharge electronic money using the payment source payment means even if the balance of electronic money, which is an available payment means, is insufficient. As a result, the payment system 1 can complete payment with the recharged electronic money. From the user's perspective, this is essentially the same as making a payment using the payment source payment means, which increases user convenience.

The payment method used to charge the available payment method in the charge process is not limited to the payment source payment method. The payment method used to charge the available payment method in the charge process may be any payment method whose payment method information is stored in the user database DB1. In other words, the charge process may be a process for charging the available payment method based on a payment method other than the payment source payment method. The user may be able to select the payment method used to charge the available payment method from window W18 in FIG. 8.

[6-2. Modification 2]
For example, the charge process of the second modification may be a process for executing a charge based on the balance of an available payment method and the payment amount of a payment. The process execution unit 105 of the second modification acquires the balance of electronic money, which is an example of an available payment method, based on the user database DB1. The process execution unit 105 acquires the payment amount included in the payment request received from the facility terminal 30. The process execution unit 105 determines the charge amount as the numerical value obtained by subtracting the acquired balance from the acquired payment amount.

The charge amount may be more than the numerical value. For example, the charge amount may be a numerical value obtained by adding a numerical value designated by the user to the numerical value. The process execution unit 105 executes the charge process by executing the charge based on the determined charge amount. The process execution unit 105 may execute the charge process by displaying the determined charge amount in the window W18, rather than by forcibly charging. The payment execution unit 106 executes the payment based on the electronic money after charging.

The recharge process of variant 2 is a process for executing a recharge based on the balance of the available payment means and the payment amount of the payment. The payment system 1 can execute a recharge based on the recharge amount required for the payment. For example, the payment system 1 can recharge electronic money using the payment source payment means only when the balance of the electronic money is insufficient.

[6-3. Modification 3]
For example, in the first and second variants, a payment facility may have multiple available payment methods. In the example of Fig. 5, the cram school has three available payment methods: points, electronic money, and a bank account. The hospital has three available payment methods: credit card, electronic money, and a financial institution account. In this case, the available payment method may be automatically selected based on the user's past usage history.

The payment system 1 of the third modified example includes a history information acquisition unit 107. The history information acquisition unit 107 acquires history information related to the payment history of the user terminal 20. For example, the history information acquisition unit 107 acquires the history information from the user database DB1. If the history information is stored in another database, another computer other than the payment server 10, or an external information storage medium, the history information acquisition unit 107 may acquire the history information from the other database, the other computer, or the external information storage medium.

The change process of variant example 3 is a process for changing the payment source to an available payment method selected based on historical information from among multiple available payment methods and executing a payment. For example, the process execution unit 105 identifies the available payment method that has been used most frequently from among multiple available payment methods based on historical information. The process execution unit 105 executes change processing for changing the payment source to the identified available payment method that has been used most frequently and executing a payment. The process execution unit 105 identifies the most recently used available payment method from among multiple available payment methods based on historical information. The process execution unit 105 executes change processing for changing the payment source to the identified most recently used available payment method and executing a payment.

For example, the process execution unit 105 may identify, based on historical information, the available payment method with the highest usage amount among multiple available payment methods. The process execution unit 105 executes a change process to change the payment source to the identified available payment method with the highest usage amount and execute the payment. The process execution unit 105 may identify, based on historical information, the available payment method with the highest usage amount among multiple available payment methods. The process execution unit 105 executes a change process to change the payment source to the identified available payment method with the highest usage amount and execute the payment.

The change process of variant example 3 is a process for changing the payment source to an available payment method selected from multiple available payment methods based on historical information and executing a payment. By selecting a payment method that the user has used in the past as an available payment method, payment system 1 can change the payment source to the most suitable payment method according to the user's tendencies.

[6-4. Modification 4]
For example, as described in the embodiment, the user can set a preferred payment method. If the user sets a preferred payment method and the preferred payment method is an available payment method, the user may be able to make a payment using only the preferred payment method without changing the payment source. Therefore, the need for a predetermined process may be determined based on the preferred payment method. The payment system 1 of the fourth modification specifies what the preferred payment method is based on the priority setting information stored in the user database DB1.

The payment system 1 of variant 4 includes a necessity determination unit 108. When a preferred payment means is set to be used in preference to the payment source payment means, the necessity determination unit 108 determines whether a specified process is required based on the balance of the preferred payment means and the payment amount of the payment. For example, the necessity determination unit 108 determines whether a specified process is required by determining whether the balance of the preferred payment means is equal to or greater than the payment amount. When the balance of the preferred payment means is equal to or greater than the payment amount, the necessity determination unit 108 determines that the specified process is not required. When the balance of the preferred payment means is less than the payment amount, the necessity determination unit 108 determines that the specified process is required.

The necessity determination unit 108 determines whether the specified process is necessary by determining whether the numerical value obtained by subtracting the payment amount from the balance of the preferred payment method is equal to or greater than a threshold value of 1. The threshold value may be fixed so that the user cannot specify it, or the user may be able to specify any value. For example, the necessity determination unit 108 determines that the specified process is unnecessary when the numerical value obtained by subtracting the payment amount from the balance of the preferred payment method is equal to or greater than the threshold value. The necessity determination unit 108 determines that the specified process is necessary when the numerical value obtained by subtracting the payment amount from the balance of the preferred payment method is less than the threshold value.

In addition, there may be multiple preferred payment methods, such as points and electronic money. In this case, the necessity determination unit 108 may determine whether or not a specified process is required based on the balance of each of the multiple preferred payment methods and the payment amount. For example, the necessity determination unit 108 may calculate the total amount of the balances of each of the multiple preferred payment methods. The necessity determination unit 108 may determine whether or not a specified process is required by determining whether or not the total amount is equal to or greater than the payment amount, or by determining whether or not the numerical value obtained by subtracting the payment amount from the total amount is equal to or greater than a threshold value that is equal to or greater than 1.

In variant 4, the payment execution unit 106 executes the payment based on the preferred payment means when the necessity determination unit 108 determines that the specified process is not required. The method of executing the payment based on the preferred payment means may be a publicly known method. For example, when the preferred payment means is points, the payment execution unit 106 executes the payment by reducing the points balance. When the preferred payment means is electronic money, the payment execution unit 106 executes the payment by reducing the electronic money balance.

The process execution unit 105 of the fourth modified example executes the predetermined process when the necessity determination unit 108 determines that the predetermined process is necessary. The process execution unit 105 executes the predetermined process based on the determination result of the facility determination unit 104 and the determination result of the necessity determination unit 108. That is, the process execution unit 105 executes the predetermined process when the facility determination unit 104 determines that the payment facility is a prohibited facility and the necessity determination unit 108 determines that the predetermined process is necessary. The process execution unit 105 does not execute the predetermined process when the facility determination unit 104 determines that the payment facility is not a prohibited facility or when the necessity determination unit 108 determines that the predetermined process is not necessary.

In the payment system 1 of the fourth variant example, when a preferred payment method is set, the payment system 1 determines whether or not a specified process is required based on the balance of the preferred payment method and the payment amount of the payment. When it is determined that the specified process is not required, the payment system 1 executes the payment based on the preferred payment method. When it is determined that the specified process is required, the payment system 1 executes the specified process. The payment system 1 can complete the payment using only the preferred payment method. For example, the user does not need to perform an operation to change the payment source, which increases user convenience.

[6-5. Modification 5]
For example, the user terminal 20 may be capable of acquiring user terminal position information relating to the position of the user terminal 20. The method of acquiring the user terminal position information itself may be a known method. For example, the user terminal 20 acquires the user terminal position information based on a method using a GNSS (Global Navigation Satellite System) receiver such as GPS, a method using the communication unit 23 (for example, a method using a mobile base station, an access point, or other wireless communication), or other methods. The user terminal position information may be latitude and longitude, coordinates, an address, base station information, access point information, or other information.

For example, the user terminal 20 transmits user terminal location information to the payment server 10. The user terminal 20 can acquire the user terminal location information at any timing. For example, the user terminal 20 can acquire the user terminal location information when the payment app is launched, while the payment app is launched, when the user performs a specified operation to instruct acquisition of user terminal location information, or at other timing. The user terminal location information may be acquired by the facility terminal 30 or other equipment (e.g., communication equipment within the facility) instead of the user terminal 20. For example, the facility terminal 30 or other equipment may acquire the user terminal location information by communicating with the user terminal 20.

The payment system 1 includes a location information acquisition unit 109. The location information acquisition unit 109 acquires user terminal location information. For example, the location information acquisition unit 109 may repeatedly acquire the latest user terminal location information. For example, the location information acquisition unit 109 acquires user terminal location information from the user terminal 20, the facility terminal 30, or other equipment (for example, communication equipment within the facility). It is assumed that facility location information relating to the location of each facility is stored in the facility database DB2 of the fifth modified example. The facility location information may be latitude and longitude, coordinates, an address, base station information, access point information, or other information.

The payment facility information acquisition unit 101 of the fifth modified example acquires a facility ID of a payment facility based on the user terminal location information. The payment facility information acquisition unit 101 identifies, from the facility database DB2, facility location information indicating a location closest to the location indicated by the user terminal location information, or facility location information indicating a location within a predetermined distance from the location indicated by the user terminal location information. The payment facility information acquisition unit 101 acquires a facility ID associated with the identified facility location information. Although the method of acquiring facility location information differs from the embodiment, other processing is similar to the embodiment.

The payment system 1 of variant 5 acquires user terminal location information from the user terminal 20. The payment system 1 acquires a facility ID based on the user terminal location information. The payment system 1 can identify the facility ID before receiving a payment request. As a result, the payment system 1 can execute a predetermined process at an earlier timing. For example, in code payment, the payment system 1 can display window W17 on the payment app screen SC1 before the code C10 is read.

[6-6. Modification 6]
For example, in the embodiment, the case where code payment is executed is taken as an example, but in the sixth modification, the case where user reading payment is executed is taken as an example.

Figure 9 is a diagram showing an example of the payment app screen SC1 in variant example 6. For example, when the user selects button B14 in the state of the payment app screen SC1 in the upper left of Figure 2, the photographing unit 26 of the user terminal 20 is activated. The payment app screen SC1 becomes the state shown in the upper left of Figure 9. The user photographs the code C40 at the payment facility with the photographing unit 26 of the user terminal 20. The facility ID is coded in the code C20. When the code C40 is displayed on the display unit 35 of the facility terminal 30, the payment amount may also be coded.

For example, the user terminal 20 acquires the facility ID by reading the code C40 generated based on the facility ID. The code C40 generated based on the facility ID is a coded code C40 of the facility ID. When the photographing unit 26 of the user terminal 20 reads the code C40, the user terminal 20 extracts the facility ID from the code C40. The user terminal 20 transmits the facility ID and the code ID stored in the user terminal 20 to the payment system 1. Here, it is assumed that the payment amount is not coded in the code C40. The payment facility information acquisition unit 101 acquires the facility ID from the user terminal 20. The user identification information acquisition unit 102 acquires the code ID from the user terminal 20.

For example, the payment server 10 receives a facility ID and a code ID from the user terminal 20. The facility determination unit 104 determines whether or not the payment store is a prohibited store. This determination method may be the same as in the embodiment. If it is determined that the payment store is not a prohibited store, the payment app screen SC1 will be in the state shown in the upper right of FIG. 9. The payment server 10 transmits data to the user terminal 20 for changing the payment app screen SC1 to that state. The user terminal 20 updates the display of the payment app screen SC1 based on that data.

For example, the user inputs the payment amount in input form F19. The user slides slide bar B20. If the payment amount is coded in code C40, the payment may be completed without performing any operation on input form F19 and slide bar B20. For example, the user terminal 20 sends a payment request including a facility ID, a code ID, and the payment amount to the payment server 10. The payment server 10 receives the payment request from the user terminal 20. The payment execution unit 106 executes the payment based on the payment request. The method of executing the payment may be similar to a known execution method.

For example, if the payment store is determined to be a prohibited store, the payment application screen SC1 will be in the state shown in the lower right of FIG. 9. The payment server 10 sends data to the user terminal 20 to set the payment application screen SC1 to that state. The user terminal 20 updates the display of the payment application screen SC1 based on that data. When the user selects button B21, electronic money is charged. When the user selects button B22, payment using points is made. When user reading payment is made, electronic money may be charged and point usage settings may be made. The payment may then be completed. In the sixth modification, if the payment facility is a prohibited facility, a message prompting the user to change the payment source may be displayed on the payment application screen SC1, as in the payment application screen SC1 in the lower right of FIG. 9. The subsequent processing is the same as in the embodiment.

In variant 6, the user terminal 20 acquires the facility ID by reading the code C40 generated based on the facility ID. The user terminal 20 transmits the facility ID and the code ID stored in the user terminal 20 to the payment system 1. The payment system 1 acquires the facility ID from the user terminal 20. The payment system 1 acquires the code ID from the user terminal 20. The payment system 1 identifies the payment source payment means based on the code ID. This allows the payment system 1 to determine whether the payment facility is a prohibited facility during the user reading and payment. The payment system 1 can execute a predetermined process based on the result of the determination of whether the payment facility is a prohibited facility during the user reading and payment.

[6-7. Modification 7]
For example, in the seventh modification, a case where self-payment is executed is taken as an example. The payment facility information acquisition unit 101 in the seventh modification acquires a facility ID from the user terminal 20. The user identification information acquisition unit 102 acquires a code ID from the user terminal 20. The identification unit 103 identifies the payment source payment means based on the code ID.

Figure 10 is a diagram showing an example of a payment app screen SC1 in Variation 7. For example, when the user selects button B15 in the state of the payment app screen SC1 in the upper left of Figure 2, the payment app screen SC1 changes to the state shown in the upper left of Figure 10. For example, the user terminal 20 transmits user terminal location information to the payment server 10. The payment server 10 receives the user terminal location information from the user terminal 20. In Variation 7, as in Variation 5, it is assumed that facility location information is stored in the facility database DB2.

For example, the payment server 10 identifies a predetermined number of facilities in the vicinity of the user terminal 20 based on the user terminal location information and facility location information. The payment server 10 transmits data of a list L23 indicating the identified facilities to the user terminal 20. The user terminal 20 displays a list L23 of multiple candidate facilities that are candidates for payment facilities based on the data. The data includes the facility IDs of the facilities included in the list L23. The list L23 may indicate predetermined facilities rather than facilities in the vicinity of the user terminal 20.

For example, the user terminal 20 identifies a candidate facility selected from the list L23 as the payment facility. When the user selects a facility from the list L23, the user terminal 20 transmits the facility ID of the facility and the code ID stored in the user terminal 20 to the payment system 1. The payment server 10 receives the facility ID and the code ID from the user terminal 20. The facility determination unit 104 determines whether the payment store is a prohibited store. This determination method may be the same as in the embodiment.

For example, if it is determined that the store to be paid is not a prohibited store, the payment app screen SC1 will be in the state shown in the upper right of Figure 10. The user inputs the payment amount in input form F24. The user slides slide bar B25. The user terminal 20 sends a payment request including the facility ID, code ID, and payment amount to the payment system 1. The payment server 10 receives the payment request from the user terminal 20. The payment execution unit 106 executes the payment based on the payment request. The method of executing the payment may be the same as a publicly known execution method.

For example, if the payment store is determined to be a prohibited store, the payment application screen SC1 will be in the state shown in the lower right of FIG. 10. The payment server 10 sends data to the user terminal 20 to change the payment application screen SC1 to that state. The user terminal 20 updates the display of the payment application screen SC1 based on that data. When the user selects button B26, electronic money is charged. When the user selects button B27, payment using points is made. Even in the case of self-payment, electronic money may be charged and points may be set for use. The payment may then be completed. In the seventh variant as well, if the payment facility is a prohibited facility, a message prompting a change of payment source may be displayed on the payment application screen SC1, as in the payment application screen SC1 in the lower right of FIG. 10.

The process execution unit 105 may execute a process to prevent prohibited facilities from being displayed in the list L23 as a predetermined process. For example, the process execution unit 105 may display prohibited facilities in the list L23, but may also display on the list L23 that the payment source payment method cannot be used. The process execution unit 105 may execute a predetermined process by controlling the display of the position column L23 on the payment app screen SC1 so that prohibited facilities are displayed after permitted facilities.

The user terminal 20 of the seventh modification displays a list L23 of multiple candidate facilities that are candidates for the payment facility. The user terminal 20 identifies a candidate facility selected from the list L23 as the payment facility. The user terminal 20 transmits the facility ID and the code ID stored in the user terminal 20 to the payment system 1. The payment system 1 acquires the facility ID from the user terminal 20. The payment system 1 acquires the code ID from the user terminal 20. The payment system 1 identifies the payment source payment means based on the code ID. This allows the payment system 1 to determine whether or not the payment facility is a prohibited facility during self-payment. The payment system 1 can execute a predetermined process based on the result of the determination of whether or not the payment facility is a prohibited facility during self-payment.

[6-8. Modification 8]
For example, even if the payment facility is a cram school, credit cards are prohibited for prepayment of tuition fees for continuous lessons, which corresponds to the provision of continuous services. Therefore, for example, credit cards are not prohibited for payment of stationery sold by the cram school and tuition fees for a one-time lesson held at the cram school. Therefore, as long as the payment system 1 can identify the merchandise to be paid for, payment based on the payment method of the payment source may be permitted even if the payment facility is a prohibited facility.

A commodity is a product or service that is the subject of payment. A commodity also includes services for which no tangible item is traded. A commodity is not limited to tangible items such as goods. A commodity can also be a class at a cram school, a medical service (medical procedure) at a hospital, a service at a beauty salon or esthetic salon, or any other service. The data storage unit 100 of variant 8 stores a commodity database DB3 that stores various information regarding each of a plurality of commodities.

Figure 11 is a diagram showing an example of product database DB3. For example, product database DB3 stores product ID, product name, category, and availability information. Product database DB3 may store any information related to the product. The information stored in product database DB3 is not limited to the example in Figure 11. For example, the price of the product may be stored in product database DB3.

The product ID is an example of product identification information that can identify a product. Therefore, any place that says product ID can be read as product identification information. Product identification information may be any information that can identify a product in some way. Product identification information is not limited to product ID. For example, product identification information may be a product name, a JAN (Japanese Article Number) code, a code uniquely assigned by a facility, a code uniquely assigned by a payment service, or other code. The product name and category may be specified by the facility or the service provider. The availability information is the same as in the embodiment.

The payment system 1 of variant 8 includes a payment product information acquisition unit 110 and a product determination unit 111. The payment product information acquisition unit 110 acquires payment product information related to the payment product in payment. The payment product is the product that is the subject of payment. Variation 8 takes as an example a case in which the product ID of the payment product corresponds to the payment product information. The payment product information may be product identification information other than the product ID, or may be a product category.

For example, when code payment is performed, the payment product information acquisition unit 110 acquires payment product information from the facility terminal 30. The facility terminal 30 acquires a product ID by reading the barcode of the product. The facility terminal 30 acquires the product ID based on product information entered by the facility staff member from the operation unit 34. The facility terminal 30 sends a payment request including the product ID of the payment product to the payment server 10. The payment product information acquisition unit 110 acquires the product ID included in the payment request received from the facility terminal 30.

When user-read payment or self-payment is performed, the payment product information acquisition unit 110 may acquire payment product information from the user terminal 20. For example, the user terminal 20 acquires a product ID by reading the barcode of the product. The user terminal 20 acquires the product ID based on product information entered by the user from the operation unit 24. The user terminal 20 sends a payment request including the product ID of the payment product to the payment server 10. The payment product information acquisition unit 110 acquires the product ID included in the payment request received from the facility terminal 30.

The product determination unit 111 determines whether the payment product is a prohibited product for which the payment source payment means is prohibited to be used. Prohibited products can also be defined as products for which the payment source payment means cannot be used. For example, the product determination unit 111 determines whether the payment product is a prohibited product based on the product database DB3. The product determination unit 111 determines whether the payment product is a prohibited product based on the usability information associated with the product ID included in the payment request and the payment source payment means identified by the identification unit 103.

For example, the product determination unit 111 determines that the payment product is a prohibited product when the usability information indicates that the use of the payment source payment means is prohibited. The product determination unit 111 determines that the payment product is a prohibited product when the usability information indicates that the payment source payment means is not usable. For example, the product determination unit 111 determines that the payment product is not a prohibited product when the usability information indicates that the payment source payment means is usable. The product determination unit 111 determines that the payment product is not a prohibited product when the usability information indicates that the use of the payment source payment means is not prohibited.

When the facility determination unit 104 determines that the payment facility is a prohibited facility and the product determination unit 111 determines that the payment product is not a prohibited product, the payment execution unit 106 does not execute payment based on the current payment source payment means based on the payment source payment means. When the facility determination unit 104 determines that the payment facility is a prohibited facility and the product determination unit 111 determines that the payment product is a prohibited product, the payment execution unit 106 does not execute payment based on the current payment source payment means.

The process execution unit 105 executes a predetermined process when the facility determination unit 104 determines that the payment facility is a prohibited facility and the product determination unit 111 determines that the payment product is a prohibited product. The process execution unit 105 does not execute a predetermined process when the facility determination unit 104 determines that the payment facility is not a prohibited facility or when the product determination unit 111 determines that the payment product is not a prohibited product.

The payment system 1 of variant 8 acquires payment product information. The payment system 1 determines whether the payment product is a prohibited product. When the payment facility is determined to be a prohibited facility and the payment product is determined to be not a prohibited product, the payment system 1 executes payment based on the payment source payment means. When the payment facility is determined to be a prohibited facility and the payment product is determined to be a prohibited product, the payment system 1 executes a predetermined process. This allows the payment system 1 to determine whether the payment product is a prohibited product. The payment system 1 can execute a predetermined process based on the result of the determination of whether the payment product is a prohibited product.

For example, even if the use of credit cards is prohibited at a cram school, if a user is trying to purchase stationery at the cram school, the user can use a credit card because the payment is not for continuous service provision. Similarly, even if the use of points is prohibited at a hospital, if a user is trying to purchase masks at the hospital, the user can use points because the payment is not for medical treatment. The payment system 1 of variant example 8 can handle such cases, thereby increasing convenience for users and payment facilities.

[6-9. Modification 9]
For example, payment system 1 may have the function related to the product described in Modification Example 8 without having the function described in the embodiment. The present disclosure also includes configurations related to other problems than the problem of "making it possible to determine whether a payment facility is a prohibited facility" described in the "Problem to be solved by the invention" section of the present disclosure. The present disclosure also includes a payment system 1 that solves other problems without solving the problem of "making it possible to determine whether a payment facility is a prohibited facility." For example, the other problem is the problem of "making it possible to determine whether a payment product is a prohibited product."

Figure 12 is a diagram showing an example of functions realized by the payment system 1 of the modified example 9. As shown in Figure 12, the payment system 1 of the modified example 9 includes an identification unit 103, a process execution unit 105, a payment product information acquisition unit 110, and a product determination unit 111. Although Figure 12 also shows the payment facility information acquisition unit 101, the user identification information acquisition unit 102, and the payment execution unit 106, the payment system 1 of the modified example 9 does not have to include at least one of the payment facility information acquisition unit 101, the user identification information acquisition unit 102, and the payment execution unit 106. The payment system 1 of the modified example 9 may include at least one of the history information acquisition unit 107, the necessity determination unit 108, and the location information acquisition unit 109.

For example, the payment product information acquisition unit 110 acquires payment product information related to the payment product for which payment is made using the user terminal 20. The method of acquiring the payment product information may be the same as in variant example 8. The identification unit 103 identifies the payment source payment means set as the payment source of the payment. The method of identifying the payment source payment means may be the same as in the embodiment. The product determination unit 111 determines whether the payment product is a prohibited product for which the use of the payment source payment means is prohibited based on the payment product information. The method of determining prohibited products may be the same as in variant example 8.

In variant example 9, the payment execution unit 106 executes the payment when the product determination unit 111 determines that the payment product is not a prohibited product. The payment execution unit 106 does not execute the payment when the product determination unit 111 determines that the payment product is a prohibited product. In this case, when there are payment products other than the prohibited products, the payment execution unit 106 may execute only the payment for the other payment products, or may not execute the payment for any payment products.

The process execution unit 105 of variant 9 executes a predetermined process when the product determination unit 111 determines that the payment product is a prohibited product. The process execution unit 105 of variant 9 differs from variant 8 in that the determination result of the facility determination unit 104 is not taken into account (the payment system 1 does not include the facility determination unit 104 in the first place), but is otherwise similar to variant 8. The process execution unit 105 does not execute a predetermined process when the product determination unit 111 determines that the payment product is not a prohibited product.

The meaning of the specified process may be the same as in the embodiment and modified examples 1 to 8. For example, when the product determination unit 111 determines that the payment product is a prohibited product, the process execution unit 105 executes a change process to change the payment source to an available payment method that can be used for the payment of the payment product and execute the payment. The embodiment differs in that the available payment method is a payment method that can be used at the payment facility or a payment method that can be used for the payment of the payment product, but other points are the same as the embodiment.

For example, if the product determination unit 111 determines that the payment product is a prohibited product, the process execution unit 105 may execute a charge process and a change process as a predetermined process, similar to variants 1 to 3. If the necessity determination unit 108 determines that a predetermined process is necessary, similar to variant 4, the process execution unit 105 may execute a predetermined process. In this case, the preferred payment method is an available payment method that can be used for the payment product. The payment system 1 of variant 9 can support any of code payment as in the embodiment, user-scanned payment as in variant 6, and self-payment as in variant 7.

The payment system 1 of variant 9 acquires payment product information. The payment system 1 identifies the payment source payment means. The payment system 1 determines whether the payment product is a prohibited product based on the payment product information. The payment system 1 executes a predetermined process when it is determined that the payment product is a prohibited product. This allows the payment system 1 to determine whether the payment product is a prohibited product. The payment system 1 can execute a predetermined process based on the result of the determination of whether the payment product is a prohibited product.

For example, if the merchandise that the user is attempting to pay for at the cram school corresponds to a continuous service provision, the payment system 1 can prohibit the use of a credit card and urge the user to change to another available payment method such as electronic money to make the payment. On the other hand, if the merchandise that the user is attempting to pay for at the cram school does not correspond to a continuous service provision, the payment system 1 can execute the payment without prohibiting the use of a credit card. The payment system 1 of variant example 9 can handle such cases, thereby improving convenience for users and payment facilities.

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

For example, at least one of the payment facility and the payment product has been given as an example of a condition for prohibiting the use of a payment means, but the condition may be other conditions. For example, the payment amount, the payment method (e.g., installment payment, lump sum payment, or bonus payment), or other conditions may exist. In this case, the payment system 1 receives data necessary for determining the condition from at least one of the user terminal 20 and the facility terminal 30. Based on the data, the payment system 1 determines whether the other condition is satisfied and executes the payment or a specified process.

For example, the functions described as being realized by the payment server 10 may be shared among multiple computers in the payment system 1. In this case, each of the multiple computers may transmit its own processing results to the other computers, thereby sharing the functions. All or part of the functions described as being realized by the payment server 10 may be realized by the user terminal 20, the facility terminal 30, or other computers. The functions described above may be realized by any computer included in the payment system 1.

[7. Notes]
For example, the payment system according to the present disclosure can be configured as follows.
(1)
a payment facility information acquisition unit that acquires payment facility information related to a payment facility where a payment is made using a user terminal;
an identification unit for identifying a payment source settlement means set as a payment source of the payment;
a facility determination unit that determines whether the payment facility is a prohibited facility in which use of the payment source payment means is prohibited based on the payment facility information;
a process execution unit that executes a predetermined process when the facility determination unit determines that the payment facility is the prohibited facility;
Payment systems including.
(2)
The processing execution unit executes, as the predetermined processing, a change processing for changing the payment source to an available payment means available at the payment facility and executing the payment.
A payment system as described in (1).
(3)
The available payment methods are payment methods that can be charged,
the processing execution unit executes, as the predetermined processing, a charge processing for charging the available payment means based on the payment source payment means, and the change processing.
A payment system as described in (2).
(4)
The charge process is a process for executing the charge based on the balance of the available payment means and the payment amount of the payment.
A payment system as described in (3).
(5)
The payment system further includes a history information acquisition unit that acquires history information regarding a payment history of the user terminal,
A plurality of the available payment methods are available at the payment facility;
the change process is a process for changing the payment source to the available payment means selected from the plurality of available payment means based on the history information, and executing the payment.
A payment system according to any one of (2) to (4).
(6)
The payment source settlement means is a credit card,
The available payment means is electronic money.
A payment system according to any one of (2) to (5).
(7)
The payment system includes:
a necessity determination unit that, when a preferred payment means is set to be used preferentially over the payment source payment means, determines whether the predetermined process is necessary based on the balance of the preferred payment means and the payment amount of the payment;
a payment execution unit that executes the payment based on the prioritized payment means when the necessity determination unit determines that the predetermined process is unnecessary;
Further comprising:
the process execution unit executes the predetermined process when the necessity determination unit determines that the predetermined process is necessary.
A payment system according to any one of (1) to (6).
(8)
The payment system further includes a location information acquisition unit that acquires user terminal location information related to a location of the user terminal,
The payment facility information acquisition unit acquires the payment facility information based on the user terminal location information.
A payment system according to any one of (1) to (7).
(9)
The user terminal displays a code based on the user identification information;
a facility terminal of the payment facility reads the code to obtain the user identification information;
the facility terminal transmits the payment facility information and the user identification information to the payment system;
The payment facility information acquisition unit acquires the payment facility information from the facility terminal,
The payment system further includes a user identification information acquisition unit that acquires the user identification information from the facility terminal,
The identification unit identifies the payment source settlement means based on the user identification information.
A payment system according to any one of (1) to (8).
(10)
the user terminal acquires the payment facility information by reading a code generated based on the payment facility information;
The user terminal transmits the payment facility information and the user identification information stored in the user terminal to the payment system;
The payment facility information acquisition unit acquires the payment facility information from the user terminal,
The payment system further includes a user identification information acquisition unit that acquires the user identification information from the user terminal,
The identification unit identifies the payment source settlement means based on the user identification information.
A payment system according to any one of (1) to (9).
(11)
The user terminal displays a list of a plurality of candidate facilities that are candidates for the payment facility,
The user terminal identifies the candidate facility selected from the list as the payment facility,
The user terminal transmits the payment facility information and the user identification information stored in the user terminal to the payment system;
The payment facility information acquisition unit acquires the payment facility information from the user terminal,
The payment system further includes a user identification information acquisition unit that acquires the user identification information from the user terminal,
The identification unit identifies the payment source settlement means based on the user identification information.
A payment system according to any one of (1) to (10).
(12)
The payment system includes:
a payment product information acquisition unit that acquires payment product information related to the payment product in the payment;
a product determination unit that determines whether the payment product is a prohibited product for which the use of the payment source payment means is prohibited;
a payment execution unit that executes the payment based on the payment source settlement means when the facility determination unit determines that the payment facility is the prohibited facility and the product determination unit determines that the payment product is not the prohibited product;
Further comprising:
The processing execution unit executes the predetermined processing when the facility determination unit determines that the payment facility is the prohibited facility and the product determination unit determines that the payment product is the prohibited product.
A payment system according to any one of (1) to (11).

1 Payment system, N Network, 10 Payment server, 11, 21, 31 Control unit, 12, 22, 32 Memory unit, 13, 23, 33 Communication unit, 20 User terminal, 24, 34 Operation unit, 25, 35 Display unit, 26, 36 Photography unit, 30 Facility terminal, 100 Data storage unit, 101 Payment facility information acquisition unit, 102 User identification information acquisition unit, 103 Identification unit, 104 Facility determination unit, 105 Processing execution unit, 106 Payment execution unit, 107 History information acquisition unit, 108 Necessity determination unit, 109 Location information acquisition unit, 110 Payment product information acquisition unit, 111 Product determination unit, 200 Data storage unit, 201 Display control unit, 202 Operation reception unit, 300 Data storage unit, 301 User identification information acquisition unit, 302 Sending section, B11, B12, B13, B14, B15, B21, B22, B26, B27 buttons, B20, B25 slide bar, C10, C20, C40 code, DB1 user database, DB2 facility database, DB3 product database, F19, F24 input form, L23 list, SC1 payment app screen, W16, W17, W18 window.

Claims (12)

a payment facility information acquisition unit that acquires payment facility information relating to a payment facility where a user visiting the payment facility makes a payment using a user terminal;
an identification unit that identifies a payment source settlement means set as a payment source of the settlement;
a facility determination unit that determines whether the payment facility is a prohibited facility in which use of the payment source payment means is prohibited based on the payment facility information;
a processing execution unit that, when the facility determination unit determines that the payment facility is a prohibited facility, executes as predetermined processing: a charging process for charging an available payment means that is available and can be charged at the payment facility based on the payment source payment means or another payment means; and a change process for changing the payment source to the available payment means and executing the payment;
Payment systems including. The charge process is a process for executing the charge based on the balance of the available payment means and the payment amount of the payment.
The payment system according to claim 1 . The payment system further includes a history information acquisition unit that acquires history information regarding a payment history of the user terminal,
A plurality of the available payment methods are available at the payment facility;
the change process is a process for changing the payment source to the available payment means selected from the plurality of available payment means based on the history information, and executing the payment.
3. A payment system according to claim 1 or 2 . The payment source settlement means is a credit card,
The available payment means is electronic money.
3. A payment system according to claim 1 or 2 . a payment facility information acquisition unit that acquires payment facility information relating to a payment facility where a user visiting the payment facility makes a payment using a user terminal;
an identification unit that identifies a payment source settlement means set as a payment source of the settlement;
a facility determination unit that determines whether the payment facility is a prohibited facility in which use of the payment source payment means is prohibited based on the payment facility information;
a necessity determination unit that, when a preferred payment means is set to be used preferentially over the payment source payment means, determines whether or not a predetermined process is necessary based on the balance of the preferred payment means and the payment amount of the payment;
a payment execution unit that executes the payment based on the prioritized payment means when the necessity determination unit determines that the predetermined process is unnecessary;
a processing execution unit that executes the predetermined processing when the facility determination unit determines that the payment facility is the prohibited facility and the necessity determination unit determines that the predetermined processing is necessary;
Payment systems including . The payment system further includes a location information acquisition unit that acquires user terminal location information related to a location of the user terminal,
The payment facility information acquisition unit acquires the payment facility information based on the user terminal location information.
6. A payment system according to claim 1 , 2 or 5 . The user terminal displays a code based on the user identification information;
a facility terminal of the payment facility reads the code to obtain the user identification information;
the facility terminal transmits the payment facility information and the user identification information to the payment system;
The payment facility information acquisition unit acquires the payment facility information from the facility terminal,
The payment system further includes a user identification information acquisition unit that acquires the user identification information from the facility terminal,
The identification unit identifies the payment source settlement means based on the user identification information.
6. A payment system according to claim 1 , 2 or 5 . the user terminal acquires the payment facility information by reading a code generated based on the payment facility information;
The user terminal transmits the payment facility information and the user identification information stored in the user terminal to the payment system;
The payment facility information acquisition unit acquires the payment facility information from the user terminal,
The payment system further includes a user identification information acquisition unit that acquires the user identification information from the user terminal,
The identification unit identifies the payment source settlement means based on the user identification information.
6. A payment system according to claim 1 , 2 or 5 . A payment system capable of communicating with a user terminal that displays a list of a plurality of candidate payment facilities and identifies a candidate facility selected from the list as the payment facility,
The user terminal transmits to the payment system payment facility information relating to the payment facility where the user who visits the payment facility makes a payment using the user terminal , and user identification information stored in the user terminal;
The payment system includes:
a payment facility information acquisition unit that acquires the payment facility information from the user terminal;
a user identification information acquisition unit that acquires the user identification information from the user terminal;
an identification unit that identifies a payment source settlement means set as a payment source of the payment based on the user identification information;
a facility determination unit that determines whether the payment facility is a prohibited facility in which use of the payment source payment means is prohibited based on the payment facility information;
a process execution unit that executes a predetermined process when the facility determination unit determines that the payment facility is the prohibited facility;
Payment systems including . a payment facility information acquisition unit that acquires payment facility information relating to a payment facility where a user visiting the payment facility makes a payment using a user terminal;
an identification unit that identifies a payment source settlement means set as a payment source of the settlement;
a facility determination unit that determines whether the payment facility is a prohibited facility in which use of the payment source payment means is prohibited based on the payment facility information;
a payment product information acquisition unit that acquires payment product information related to the payment product in the payment;
a product determination unit that determines whether the payment product is a prohibited product for which the use of the payment source payment means is prohibited;
a payment execution unit that executes the payment based on the payment source settlement means when the facility determination unit determines that the payment facility is the prohibited facility and the product determination unit determines that the payment product is not the prohibited product;
a process execution unit that executes a predetermined process when the facility determination unit determines that the payment facility is the prohibited facility and the product determination unit determines that the payment product is the prohibited product;
Payment systems including . The computer
a payment facility information acquisition step of acquiring payment facility information relating to a payment facility where a user visiting the payment facility makes a payment using a user terminal;
a step of identifying a payment source payment means set as a payment source of the payment;
a facility determination step of determining whether or not the payment facility is a prohibited facility in which use of the payment source payment means is prohibited based on the payment facility information;
a processing execution step of executing, as predetermined processing, a charging process for charging an available payment means that is available and can be charged at the payment facility based on the payment source payment means or another payment means when the payment facility is determined to be the prohibited facility by the facility determination step, and a change process for changing the payment source to the available payment means and executing the payment ;
The payment method to be performed. a payment facility information acquisition unit that acquires payment facility information relating to a payment facility where a user visiting the payment facility makes a payment using a user terminal;
An identification unit for identifying a payment source settlement means set as a payment source of the settlement;
a facility determination unit that determines whether or not the payment facility is a prohibited facility in which use of the payment source payment means is prohibited based on the payment facility information;
a processing execution unit that, when the facility determination unit determines that the payment facility is the prohibited facility, executes as predetermined processing: a charging process for charging an available payment means that is available and can be charged at the payment facility based on the payment source payment means or another payment means; and a change process for changing the payment source to the available payment means and executing the payment.
A program that makes a computer function as a

Images