Payment system, payment server, and payment method

Abstract

To provide a payment system, a payment method, and an application program capable of dealing with various events. [Solution] A payment server acquires store input information related to payment from a store payment terminal, and transmits payment information corresponding to the store input information and the tag ID received from the application program to the application program which is the source of the tag ID, and the application program displays the payment information on a user terminal device and accepts the user's operation to accept payment. A payment system in which the payment server differs in processing based on the relationship between the timing at which the tag ID was acquired from the application program and the timing at which the store input information was acquired from the store payment terminal.

Description

[Technical field]

[0001] The present invention relates to a payment system, a payment server, and a payment method. [Background technology]

[0002] Conventionally, an invention for a payment system has been disclosed that includes an application program that runs on a user terminal device with NFC functionality and a payment server that communicates with the application program, in which the application program causes the user terminal device to transmit a tag ID to the payment server when the tag ID is acquired by the NFC function from an NFC tag that is installed in a store and stores a tag ID that can recognize at least some of the store, the store payment terminal installed in the store, and the affiliated stores to which the store belongs, and the payment server transmits payment information corresponding to the tag ID received from the application program to the application program, and the application program causes the user terminal device to display the payment information and accept a payment approval operation by the user. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 7571343 Summary of the Invention [Problem to be solved by the invention]

[0004] In actual payment scenarios, it is possible that the user's identity may become unclear as time passes after information is entered into the store's payment terminal, or that a user other than the purchaser may mistakenly read the tag ID. Conventional technologies have not taken into consideration how to deal with such various events.

[0005] The present invention has been made in consideration of the above circumstances, and one of its objects is to provide a payment system, a payment method, and an application program that can handle a variety of events. [Means for solving the problem]

[0006] One aspect of the present invention is a payment system comprising an application program running on a user terminal device having an NFC (Near Field Communication) function, and a payment server communicating with the application program, wherein the application program causes the user terminal device to transmit, when a tag ID is acquired by the NFC function from an NFC tag that is installed in a store and stores a tag ID capable of recognizing at least some of the store, a store payment terminal installed in the store, and the affiliated stores to which the store belongs, the tag ID to the payment server, the payment server acquires store input information related to the payment from the store payment terminal, and transmits the store input information and payment information corresponding to the tag ID received from the application program to the application program that is the source of the tag ID, the application program causes the user terminal device to display the payment information and accept a payment approval operation by a user, and the payment server differs in processing based on the relationship between the timing at which the tag ID was acquired from the application program and the timing at which the store input information was acquired from the store payment terminal. Effect of the Invention

[0007] According to one aspect of the present invention, it is possible to provide a payment system, a payment method, and an application program that can handle various events. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 illustrates basic aspects of brick-and-mortar electronic payment. [Diagram 2]FIG. 1 is a diagram showing an example of a configuration for performing electronic payment (terminal payment) using a payment application. [Diagram 3] FIG. 13 is a diagram showing an example of the contents of user information 172. [Figure 4] FIG. 13 is a diagram showing an example of the contents of affiliated store / store information 174. [Diagram 5] FIG. 13 is a diagram showing an outline of a process flow when a user scan is performed. [Figure 6] FIG. 13 is a diagram showing an overview of the process flow when a store scan is performed. [Figure 7] FIG. 1 is a diagram showing an example of a configuration for performing electronic payment (card payment) using a payment card. [Figure 8] FIG. 1 is a diagram illustrating a store-entry type NFC payment. [Figure 9] FIG. 11 is a sequence diagram showing an example of a processing flow of a store-entry type NFC payment. [Figure 10] FIG. 11 is a diagram showing an example of screen transitions of the payment application 20 when a store-input type NFC payment is performed. [Figure 11] 11 is a flowchart showing an example of a flow of processing executed by the payment server 100 regarding NFC payment. [Figure 12] FIG. 2 is a diagram showing an example of a first scene realized by the payment server 100. [Figure 13] FIG. 11 is a diagram showing an example of a second scene realized by the payment server 100. [Figure 14] FIG. 13 is a diagram showing an example of a third scene realized by the payment server 100. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] [overview] Hereinafter, with reference to the drawings, an embodiment of a payment system, a payment method, and an application program according to the present invention will be described. The application program, a payment server, and a credit card server work together to provide an electronic payment service. In the following description, the application program is referred to as a payment application. The combination of the payment server and the credit card server may be referred to as a payment management system. The electronic payment service is a service that supports payments related to the purchase of goods and services at a store. The store is, for example, a physical store (real store) that exists in the real world, but may also include a virtual store for electronic commerce. The virtual store may include a store provided by an entity different from the operator of the electronic payment service. In that case, when making a payment for shopping at the virtual store, the screen is controlled to transition to an interface screen of the electronic payment service. In the electronic payment service, the store is treated as belonging to, for example, an affiliated store (brand), and processing such as payment when a purchase is made at the store is mainly performed between the user and the affiliated store. Alternatively, processing such as payment may be performed between the user and the store.

[0010] [Electronic payment methods at brick-and-mortar stores] FIG. 1 is a diagram showing a basic aspect of a brick-and-mortar electronic payment. Basically, electronic payment is performed by three parties: a medium M held by a user U, a store facility E, and a payment system S. The medium M is a portable computer device such as a smartphone, a credit card, etc. The store facility E is present in a physical brick-and-mortar store (hereinafter simply referred to as a store) that exists in real space, and is a POS device, a wireless communication device, a credit card reader, a printed matter of a code image such as a QR code (registered trademark), or a display device that displays a code image. In a brick-and-mortar electronic payment, first, information that can recognize the user's identification information and information on the payment amount are shared unidirectionally or bidirectionally between the medium M and the store facility E. At this time, one of the medium M or the store facility E optically reads various information from a code image displayed by the other, information is provided by NFC (Near Field Communication), or a PAN (Primary Account Number) is read by a credit card reader. Then, one of the medium M or the store facility E (the side that acquires information from the other) transmits payment information required for payment to the payment system S via the network NW. Both the medium M and the store equipment E may transmit some information to the payment system S. The payment system S manages various information of the user U and performs electronic payment between the store and the user U in various ways. Electronic payment is performed by one or both of a prepaid system and postpay, or by other methods. In addition, electronic payment may also include the so-called online shopping mode, which is performed by both the user's terminal device and the payment system. The network NW includes, for example, the Internet, a LAN (Local Area Network), a wireless base station, a provider device, etc. Various devices that communicate via the network NW, which will be described later, are assumed to have communication devices such as network cards and wireless communication modules.

[0011] [Configuration (Terminal Payment)] 2 is a diagram showing an example of a configuration for performing electronic payment (terminal payment) using a payment app. This electronic payment is executed mainly by a payment app 20 that operates on a user terminal device 10 that is one of the media M, one or more store payment terminals 30 and one or more store code images 40 that are one of the store facilities E, a payment server 100 that constitutes a part of a payment system S, and the like. The payment server 100 communicates with the user terminal device 10, the store payment terminal 30, and one or more information terminals 50 via a network NW.

[0012] The user terminal device 10 is, for example, a portable terminal device such as a smartphone or a tablet terminal. The user terminal device 10 is a computer device having at least an optical reading function, a communication function, a display function, an input acceptance function, and a program execution function. In the following description, components for realizing these functions are referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), etc. In the user terminal device 10, a processor such as a CPU executes a payment application 20, thereby operating to provide an electronic payment service to a user in cooperation with a payment server 100. The payment application 20 is, for example, installed in the user terminal device 10 from an application distribution server (not shown), and controls the camera, communication device, touch panel, etc. of the user terminal device 10.

[0013] The store payment terminal 30 is installed, for example, in a store. The store payment terminal 30 is a computer device (or a collection of these) having at least a product price acquisition function, an optical reading function, a program execution function, and a communication function. The store payment terminal 30 includes a so-called POS (Point of Sale) device, and the POS device may have a product price acquisition function and an optical reading function.

[0014] The store code image 40 is placed in a store and is a code image such as a QR code (registered trademark) printed on a medium such as paper or plastic. The store code image 40 may be displayed on a display placed in the store (or on a display of a terminal device such as a smartphone or tablet terminal).

[0015] The information terminal 50 is used by the operator of the affiliated store who manages the stores. In the electronic payment service, a customer who is a provider of goods or services is treated as an affiliated store (brand), and one or more stores exist under the affiliated store. An affiliated store that operates only one store may exist. The information terminal 50 is a smartphone, a tablet terminal, a personal computer, or the like. The information terminal 50 operates an interface 55 for affiliated stores. The interface 55 for affiliated stores may be an app for affiliated stores, or may be a web page displayed by a general-purpose browser. The interface 55 for affiliated stores accepts coupon settings and the like by the operator of the affiliated store and transmits them to the payment server 100. The information terminal 50 may have a function of displaying a code image equivalent to the store code image 40 or reading a code image displayed by the user terminal device 10 by executing the interface 55 for affiliated stores (in the latter case, an optical reading function is required).

[0016] The payment server 100 communicates with the credit card server 200 via a network NW. The payment server 100 has, for example, a content provider 110, an information manager 120, a payment processor 130, and a memory unit 170. The components other than the memory unit 170 are realized by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be implemented using a large scale integration (LSI), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like. The program may be realized by hardware (including circuitry) such as a Gate Array (GPU) or a Graphics Processing Unit (GPU), or may be realized by a combination of software and hardware. The program may be stored in advance in a storage device (a storage device having a non-transient storage medium) such as a Hard Disk Drive (HDD) or a flash memory, or may be stored in a removable storage medium (non-transient storage medium) such as a DVD or CD-ROM, and installed in the storage device by mounting the storage medium in a drive device.

[0017] The storage unit 170 is a hard disk drive (HDD), a flash memory, a random access memory (RAM), or the like. The storage unit 170 may be a network attached storage (NAS) device that the payment server 100 can access via a network. The storage unit 170 stores information such as user information 172 and affiliated store / shop information 174. The storage unit 170 may also store tag ID mapping information 176. This will be described in the section [NFC payment].

[0018] The content providing unit 110 has, for example, a function of a web server, and provides information (content) for displaying various screens of the electronic payment service to the user terminal device 10. The content providing unit 110 provides the content in the form of a web page to the user terminal device 10, and provides the parameters required for the payment application 20 to render an image to the user terminal device 10.

[0019] The information management unit 120 manages user information 172 and affiliated store / shop information 174 by editing, adding, deleting, etc.

[0020] 3 is a diagram showing an example of the contents of user information 172. User information 172 is information in which, for example, user URL, account ID, phone number, password, registration date, charge balance, electronic money type, terminal payment method, card payment method, various history information, identity verification flag, name, address, date of birth, email address, bank account, deferred payment settings, deferred payment condition information, etc. are associated with each other. Hereinafter, a user instance (electronic payment account) in which such information is associated may be referred to as an account. In the figure, items marked with "-" indicate that they are not set.

[0021] The user URL is used for the remittance process between users. When registering for the electronic payment service, it is necessary to register a phone number and a password. The account ID is issued to the user by the payment server 100. The registration date is the date on which the user registered for the electronic payment service (the date on which the account was created). The charge balance is information indicating the balance of electronic money that is set by the user remitting money to the account in advance. Remittance methods include depositing money into an ATM (Automatic Teller Machine) of a designated company (bank) and remittance from a registered bank account. The type of electronic money is information indicating, for example, whether the electronic money can be withdrawn or can only be used for electronic payment. The terminal payment method is setting information indicating whether the user will make electronic payment using the charge balance (balance payment) or deferred payment in terminal payment. The card payment method is setting information indicating whether the user will make electronic payment using the charge balance (balance payment) or deferred payment in card payment. The various historical information includes charge history, which is a history of when a user has previously transferred money to an electronic payment service to increase their charge balance, and payment history, which shows the details of payments made by the user for each payment (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.).

[0022] The identity verification flag is information indicating whether or not the user has completed identity verification using an identification document. Deferred payment can be selected when identity verification has been completed, and since the user with the account ID "002" in the figure has not completed identity verification, the user can only select balance payment as the terminal payment method. The bank account is the account number of a bank account that can be used to deposit funds into the electronic payment service. Deferred payment settings is information indicating whether or not the setting operations for making deferred payment selectable have been completed. Deferred payment condition information is information indicating various conditions such as the limit on deferred payment and the amount used in the current month.

[0023] FIG. 4 is a diagram showing an example of the contents of affiliated store / store information 174. The affiliated store / store information 174 includes, for example, a first table 174A in which an affiliated store ID and a store ID are associated with a store URL, a second table 174B in which an affiliated store name and sales amount (described above) are associated with an affiliated store ID, and a third table 174C in which a store ID is associated with a store ID. In addition to the above information, the affiliated store / store information 174 may also include information such as the category of the affiliated store or store, the location of the store, and payment patterns. As shown in the figure, the third table 174C may further include identification information (device ID) of the store payment terminal 30 in the store associated with each store.

[0024] The payment processing unit 130 performs various processes for electronic payment. There are two methods for terminal payment: a first method (user scan) and a second method (store scan), which will be described below.

[0025] FIG. 5 is a diagram showing an outline of the process flow when a user scan is performed. First, the user terminal device 10 with the payment application 20 running reads and decodes the store code image 40 by using an optical reading function (S1). The store code image 40 includes store URL information. The payment application 20 transmits the first payment information including the store URL and the user's account ID to the payment server 100 (S2). The payment server 100 searches the affiliated store / store information 174 using the affiliated store ID and store ID corresponding to the store URL, acquires the affiliated store name and store name information (S3), and transmits it to the payment application 20 (S4). The user inputs the payment amount to the payment application 20 on the screen displaying the affiliated store name and store name (S5). The payment application 20 then generates the second payment information including at least the payment amount, and transmits it to the payment server 100 (S6).

[0026] If the "Terminal Payment Method" in the user information 172 of the user is set to "Balance Payment", the payment processing unit 130 of the payment server 100 performs electronic payment based on the received second payment information (S7-1). At this time, the payment processing unit 130 performs electronic payment by, for example, decreasing the charge balance managed in association with the user ID and increasing the item value of the affiliated store's sales. The item value of the affiliated store's sales is not used as electronic money itself, for example, but an amount corresponding to the item value of the sales is transferred to a bank account in a cycle according to an agreement between the affiliated store and the electronic payment service. On the other hand, if the "Terminal Payment Method" is set to "Postpaid", the payment processing unit 130 transmits the first payment information and the second payment information to the credit card server 200 to request electronic payment (S7-2). The credit card server 200 performs electronic payment by adding the payment amount to the monthly usage amount of the user based on the received information and deducting the monthly usage amount from the user's bank account after the closing date (S7-3).

[0027] Then, the payment processing unit 130 sends a payment completion notice (information for displaying a payment completion screen) to the payment application 20 via the content providing unit 110 (S8), and the payment application 20 displays the payment completion screen (S9). When the store code image 40 is displayed on a display placed in a store, the store code image 40 may include not only the store URL but also information on the payment amount. In this case, the step of the user inputting the payment amount is omitted, and the information on the payment amount is included in the first payment information and sent to the payment server 100. Information on the affiliated store name and store name may be included and displayed on the payment completion screen.

[0028] FIG. 6 is a diagram showing an outline of the process flow when a store scan is performed. First, when the payment application 20 is started, when a payment operation is performed in the payment application 20, when an automatic update timing (for example, every minute) occurs, and at other timings, the payment application 20 transmits a request for issuing a one-time code to the payment server 100 (S11). The payment processing unit 130 of the payment server 100 generates a one-time code (S12) and transmits it to the payment application 20 (S13). The payment application 20 displays a code image such as a QR code or a barcode generated based on the one-time code (S14). The user holds (presents) the display surface of the user terminal device 10 over the store payment terminal 30, and the store payment terminal 30 reads and decodes the code image by an optical reading function to obtain the one-time code, etc. (S15). Then, the store payment terminal 30 generates payment information including the one-time code, payment amount, affiliated store ID, store ID, etc., and transmits it to the payment server 100 (S16). The payment amount information is acquired in advance by reading a bar code or by manually entering the information.

[0029] The payment processing unit 130 of the payment server 100 identifies the user corresponding to the one-time code based on the received information, and if the "Terminal payment method" in the user information 172 of the user is set to "Balance payment", performs electronic payment based on the received second payment information (S17-1). The content of the process at this time is the same as the process of S7-1 in FIG. 5. On the other hand, if the "Terminal payment method" is set to "Deferred payment", the payment server 100 transmits the first payment information and the second payment information to the credit card server 200 to request electronic payment (S17-2). The credit card server 200 adds the payment amount to the user's monthly usage amount based on the received information, and performs electronic payment by deducting the monthly usage amount from the user's bank account after the closing date (S17-3).

[0030] Then, the payment processing unit 130 transmits a payment completion notification to the payment application 20 via the content providing unit 110 (S18), and the payment application 20 displays a payment completion screen (S19).

[0031] Note that electronic payment may be performed using only one of the above patterns. Furthermore, the "account ID" described in FIG. 2 may be other information (e.g., a phone number) that can be used as user identification information. Furthermore, issuance of a one-time code may be omitted in the store scan, and the payment application 20 may display a code image generated based on the user's account ID. In this case, the payment server 100 identifies the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[0032] Note that the "deferred payment" settlement may be performed within the settlement server 100, rather than being managed by the credit card server 200. In this case, the components such as the settlement card 60 and the credit card server 200 may be omitted.

[0033] [Configuration (card payment)] 7 is a diagram showing an example of a configuration for performing electronic payment (card payment) using a payment card. This electronic payment is performed mainly with a payment card 60, which is one of the media M, a credit card processing terminal 70, which is one of the store facilities E, a payment server 100 and a credit card server 200, which constitute a part of a payment system S. The credit card server 200 communicates with the credit card processing terminal 70 via a network NW.

[0034] The credit processing terminal 70 is installed in the store, similar to the store payment terminal 30. The credit processing terminal 70 includes, for example, a credit card payment terminal (credit card reader) and a POS device. The credit card payment terminal reads a PIN (Personal Identification Number) from an inserted or held credit card and collates it with the PIN entered by the user, or transmits a PAN (Primary Account Number) read from the credit card to the credit card server 200 via the POS device. The POS device cooperates with the credit card payment terminal to transmit information such as the payment amount to the credit card server 200. A payment agent server (acquirer) may be interposed between the credit card processing terminal 70 and the credit card server 200, but in the following, the description of the payment agent server will be omitted for the sake of simplicity. The payment card 60 is, for example, of the same type as a commonly used credit card, and has a communication chip embedded in the card substrate. The communication chip has a built-in storage medium that stores the PIN, and communicates with an external device via a contactor (or a wireless antenna). Alternatively, the payment card 60 may be a magnetic card. The information (message) sent and received when using a credit card includes an authorization message for authentication and a sales message for conveying the payment amount, but detailed explanations distinguishing between these will be omitted below.

[0035] The credit card server 200 communicates with the payment server 100 via the network NW. The credit card server 200 has, for example, an information management unit 210, a credit interface 220, a payment allocation unit 230, a credit payment processing unit 240, and a storage unit 270. The components other than the storage unit 270 are realized, for example, by a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuitry) such as an LSI, ASIC, FPGA, or GPU, or may be realized by cooperation between software and hardware. The program may be stored in a storage device (storage device having a non-transient storage medium) such as an HDD or flash memory in advance, or may be stored in a removable storage medium (non-transient storage medium) such as a DVD or CD-ROM, and may be installed in the storage device by mounting the storage medium in a drive device. Information such as card user information 272 is stored in the storage unit 270.

[0036] The information management unit 210 manages the card user information 272 by editing, adding, deleting, etc. The card user information 272 is information in which, for example, information unique to a user (e.g., PAN), a card payment method, and the user's account ID (used by the payment server 100) are associated with each other. The card payment method is setting information indicating whether the user will make electronic payment using the charge balance (balance payment) or deferred payment in card payment.

[0037] The credit interface 220 determines whether the BIN (Bank Identification Number) in the PAN included in the message received from the credit processing terminal 70 is a code for its own company, and if it is, passes the message received from the credit processing terminal 70 to the payment allocation unit 230, and if it is not a code for its own company, discards the received message.

[0038] The payment allocation unit 230 refers to the card user information 272 of the user corresponding to the message obtained from the credit interface 220, and judges whether the "card payment method" is set to "deferred payment". If the "card payment method" is set to "deferred payment", the payment allocation unit 230 notifies the credit interface 220 of that fact, and passes the message obtained from the credit interface 220 to the credit payment processing unit 240. On the other hand, if the "card payment method" is set to "balance payment", the payment allocation unit 230 adds the account ID of the user to the message obtained from the credit interface 220 and sends it to the payment server 100 to request electronic payment. The payment server 100 that has been requested to make electronic payment performs the same process as S7-1 in FIG. 5 and S17-1 in FIG. 6.

[0039] The credit interface 220 checks the PAN and expiration date, and checks whether the cumulative payment amount exceeds the upper limit for the current month, etc. The credit payment processing unit 240 adds the payment amount to the user's monthly usage amount based on the information contained in the message obtained from the payment allocation unit 230, and performs electronic payment by deducting the monthly usage amount from the user's bank account after the closing date.

[0040] [NFC payment] The payment system can perform payment using NFC (hereinafter, NFC payment) in addition to the terminal payment and card payment described above. This will be described below. The payment system may also be one that exclusively performs NFC payment. There are two types of NFC payment: store input type and user input type, but the present invention exclusively relates to the store input type.

[0041] (Store input type) FIG. 8 is a diagram showing a typical store-input type NFC payment. In the store-input type NFC payment, a store clerk T inputs a payment amount into a store payment terminal 30, which is a POS device, by reading a barcode or manually inputting the amount. The input information (input information) is transmitted to a payment server 100. An object having an NFC tag 80 built therein or to which an NFC tag 80 is attached is placed in the vicinity of the POS device (alternatively, the NFC tag 80 may be attached to the store payment terminal 30). The NFC tag 80 is an independent NFC tag that is not an internal function of the store payment terminal 30. The NFC tag 80 is, for example, a passive type tag that does not have its own power source, and is configured to start up when power is supplied from an external device and transmit information (tag ID) stored in its own memory. When a user holds a user terminal device 10 having an NFC function over the NFC tag 80, the user terminal device 10 acquires the tag ID, and the payment application 20 causes the user terminal device 10 to transmit the tag ID to the payment server 100. The tag ID is information that can identify at least a part of the store, the store payment terminal 30 (POS device) installed in the store, and the affiliated store to which the store belongs. The payment server 100 maps (associates) the tag ID with the store, the store payment terminal 30 installed in the store, or the affiliated store to which the store belongs, selects input information received from the store corresponding to the received tag ID, and transmits payment information to the payment application 20 based on the input information. This allows the payment application 20 to obtain payment information without directly communicating with the store payment terminal 30, and to accept the user's operation of payment approval (such as the operation of the "Pay" button). This type of payment can be realized even if the store payment terminal 30 does not support NFC. As a result, the convenience of electronic payment can be improved in a practical sense.

[0042] There are two possible ways to associate a tag ID with a store or affiliated store. (1) A method of rewriting the tag ID to some kind of ID information assigned to the store, the store payment terminal 30, or the affiliated store, or to information corresponding thereto (which has been edited, simplified, etc.). Some ID information given to a store or affiliated store is, for example, the device ID of the store payment terminal 30 (POS device). The ID information may also be a login ID for the affiliated store interface 55, or the affiliated store ID or store ID shown in FIG. 4. The ID information may also include a combination of the above. In this case, a process of rewriting the ID information in the NFC tag 80 is performed at the start of operation, for example, using the information terminal 50. (2) The tag ID is any information (for example, the information remains as it is at the time the NFC tag 80 is purchased), and the tag ID mapping information 176 manages the association between the tag ID and the store, the store payment terminal 30, or the affiliated store. In this case, the store or affiliated store reads the tag ID from the NFC tag 80 and registers it in the tag ID mapping information 176 of the payment server 100 using, for example, the affiliated store interface 55. The tag ID mapping information 176 is information in which the tag ID is associated with some or all of the device ID, affiliated store ID, and store ID. When the tag ID is sent from the user terminal device 10, the payment server 100 searches the tag ID mapping information 176 using the tag ID to identify some or all of the affiliated store, store payment terminal 30, and store.

[0043] FIG. 9 is a sequence diagram showing an example of the flow of the process of store-input type NFC payment. Here, it is assumed that the tag ID has already been associated with the store or affiliated store. First, store input information is generated in the store terminal device 30 (S21). The store input information is information input to the store terminal device 30 by reading a barcode, manually inputting, or the like. The store payment terminal 30 transmits the store input information to the payment server 100 (S22). In parallel with this, the user holds the user terminal device 10 over the NFC tag 80, and the user terminal device 10 (payment application 20) acquires the tag ID (S23). The order of the processes of S21 and S22 and S23 may be limited to the order in which the store input information is generated and then the user holds the user terminal device 10 over the NFC tag 80, but as described later, a flow in which the user holds the user terminal device 10 over the NFC tag 80 first and then the store input information is generated may be allowed. Conversely, the flow may be limited to one in which the user first holds the user terminal device 10 over the NFC tag 80 and then the store input information is generated.

[0044] Next, the user terminal device 10 (payment application 20) transmits information including the tag ID to the payment server 100 (S24). For example, the payment processing unit 130 of the payment server 100 identifies the store or affiliated store from the tag ID (S25), and transmits payment information based on the input information and the information of the identified store or affiliated store to the payment application 20 (S26). The payment information includes at least the payment amount and the information of the store or affiliated store, and may further include the date and time of payment, points to be awarded, campaign information, etc. If the tag ID includes information associated with the device ID in the tag ID mapping information 176 or the device ID, the store or affiliated store can be identified by referring to the third table 174C. In addition, if the tag ID is information associated with the device ID in the tag ID mapping information 176 or the device ID, the payment amount can be obtained from the most recent unsettled input information of the store payment terminal 30 corresponding to the device ID. If the tag ID does not include a device ID or information associated with the device ID in the tag ID mapping information 176, the payment amount may be specified based on the relationship between the input information and the time when the tag ID was acquired, the location information or Wi-Fi connection information of the user terminal device 10, or other information. Thus, in the store input type, the tag ID may be information that can identify the payment amount of the transaction for which electronic payment is to be made.

[0045] Upon receiving the payment information, the payment application 20 accepts the operation of accepting the payment (S27), and when the operation is performed, sends a payment OK notification to the payment server 100 (S28). The payment processing unit 130 of the payment server 100 performs the payment process (S29). This payment process may be performed according to the user's setting of the "terminal payment method" as in the processes of S7-1 to S7-3 in FIG. 5 or S17-1 to S17-3 in FIG. 6. Upon completion of the payment process, the payment processing unit 130 of the payment server 100 sends a payment completion notification to each of the payment application 20 and the store payment terminal 30 and / or the information terminal 50 (S30, 31).

[0046] 10 is a diagram showing an example of screen transitions of the payment application 20 when a store-input type NFC payment is made. When an NFC tag 80 is detected while the NFC function of the user terminal device 10 is activated, screen IM1 is displayed. Screen IM1 is provided with a button B1 for accepting an operation to proceed with the NFC payment. When button B1 is operated, screen IM2 is displayed. Note that depending on the type of OS (Operating System) of the user terminal device 10, the display of screen IM1 may be omitted, and when an NFC tag 80 is detected while the NFC function of the user terminal device 10 is activated, screen IM2 is displayed.

[0047] Screen IM2 includes an area A1 where the payment amount is displayed. At this point, the processing up to S26 in FIG. 9 has been completed. Screen IM2 has a button B2 for accepting a payment approval operation. When button B2 is operated, screen IM3 is displayed. This screen IM3 is a screen based on the payment completion notification of S30 in FIG. 9. Screen IM3 has a button B3 for transitioning to a full-function display of payment application 20, and when button B3 is operated, screen IM4, which is a payment completion notification screen similar to that in the case of terminal payment described above, is displayed. Screen IM4 displays additional information such as earned points and campaign information.

[0048] Here, the number of operations required to complete NFC payment is, for example, one or two, as shown in Fig. 10. In contrast, the operations required to perform terminal payment include at least three operations: starting up payment application 20, issuing a scan instruction, and accepting payment. Therefore, the number of operations required to complete NFC payment is fewer than the number of operations required to perform terminal payment, and the user can complete the payment with fewer operations. As a result, user convenience can be improved.

[0049] The following describes the processes corresponding to various events in NFC payment. As described below, the payment processing unit 130 of the payment server 100, for example, performs different processes based on the relationship between the timing of acquiring the tag ID from the payment application 20 and the timing of acquiring the store input information from the store payment terminal 30.

[0050] FIG. 11 is a flowchart showing an example of the flow of processing executed by the payment server 100 for NFC payment. First, the payment server 100 judges whether or not the store input information is acquired from the store payment terminal 30 (S50). When the store input information is acquired from the store payment terminal 30, the payment server 100 starts counting the first valid period T1 (S51). The start point of the count may be the acquisition point of the store input information, or the time of the timestamp if the store input information is assigned a timestamp indicating the input point. Next, the payment server 100 judges whether or not the first valid period T1 has elapsed since the start point of the count (S52). The first valid period T1 is, for example, a time of several seconds to a dozen seconds. When the first valid period T1 has elapsed since the start point of the count, the payment server 100 resets the store input information and tag ID acquired at that time, and ends the processing of one routine of this flowchart. Then, the processing is resumed from S50. Similarly, in the following case where it is written "the processing of one routine of this flowchart ends," it is assumed that the store input information and tag ID are reset and the processing is restarted.

[0051] If it is determined in S52 that the first valid period T1 has not elapsed, the payment server 100 determines whether or not a tag ID has been acquired from the payment application 20 (S53). If the tag ID has not been acquired, the process returns to S52. If the tag ID has been acquired, the payment server 100 transmits payment information (see S25-S26 in FIG. 9) to the payment application 20 (S54). Next, the payment server 10 determines whether or not a payment cancellation notice has been acquired from the payment application 20 (S55). If a payment cancellation notice has been acquired from the payment application 20, the process returns to S52. Here, in the process of S53 executed after the process returns to S52, the payment application 20 that transmits the tag ID may be the same as or different from the payment application 20 that initially transmitted the tag ID. Examples of the latter scenario may include a case where a user (for example, by mistake) reads a tag ID using the payment app 20 and sends it to the payment server 100, and then another user reads the tag ID using the payment app 20 and sends it to the payment server 100, or a case where a user who owns multiple user terminal devices 10 reads a tag ID using the payment app 20 of a first user terminal device 10 and sends it to the payment server 100, and then reads the tag ID using the payment app 20 of a second user terminal device 10 and sends it to the payment server 100.

[0052] If the payment cancellation notice is not received from the payment application 20, the payment server 100 judges whether or not the first valid period T1 has elapsed since the counting start time (S56). If the first valid period T1 has elapsed since the counting start time, the payment server 100 ends the processing of one routine of this flowchart.

[0053] If it is determined in S56 that the first valid period T1 has not elapsed, the payment server 100 determines whether or not a payment approval notice has been obtained from the payment application 20 (S57). If a payment approval notice has been obtained from the payment application 20, the payment server 100 performs payment processing (S58). This ends the processing of one routine of this flowchart.

[0054] On the other hand, if the store input information is not acquired in S50, the payment server 100 judges whether or not the tag ID is acquired from the payment application 20 (S59). If the tag ID is not acquired, the process returns to S50. If the tag ID is acquired, the payment server 100 starts counting the second validity period T2 (S60). The start point of the count may be the time when the tag ID is acquired, or the time of the timestamp if the tag ID is assigned with a timestamp indicating the time of reading. The second validity period T2 may be set to, for example, a period of several seconds to a dozen seconds, which is shorter than the first validity period T1.

[0055] Next, the payment server 100 judges whether or not the second valid period T2 has elapsed since the start of counting (S61). If the second valid period T2 has elapsed since the start of counting, the payment server 100 ends the processing of one routine of this flowchart. If the second valid period T2 has not elapsed since the start of counting, the payment server 100 judges whether or not the same tag ID has been acquired from a payment application 20 other than the payment application 20 that transmitted the tag ID in S59 (S62). If a positive judgment result is obtained in S62, the payment server 100 resets the count of the second valid period T2 once and starts counting from zero (S60).

[0056] If a negative determination result is obtained in S62, the payment server 100 determines whether or not store input information has been acquired from the store payment terminal 30 (S63). If store input information has been acquired from the store payment terminal 30, the process returns to S51. If store input information has not been acquired from the store payment terminal 30, the process returns to S61.

[0057] The following describes the functions of the payment server 100 that are realized based on the processing of the flowchart exemplified above. First, the payment server 100 starts counting the first valid period based on the time when the store input information is acquired from the store payment terminal 30, and invalidates the payment related to the store input information when the first valid period has elapsed (Yes in S52 in FIG. 11).

[0058] In addition, since the payment server 100 resets the store input information and the tag ID after performing the payment process, it is possible to prevent a case where another payment application 20 mistakenly performs the payment thereafter. FIG. 12 is a diagram showing an example of a first scene realized by the payment server 100. After a payment operation (operation to accept the payment) is performed in the first payment application 20-1, even if the second payment application 20-2 reads the tag ID and transmits it to the payment server 100, the payment information is not transmitted to the second payment application 20-2. As a result, the screen for NFC payment is not displayed in the second payment application 20-2, and another screen is displayed.

[0059] In addition, the payment server 100 acquires store input information from the store payment terminal 30, transmits payment information to the first payment application 20-1 that is the sender of the tag ID, and transmits payment information to the second payment application 20-2 if the tag ID is received from the second payment application 20-2 before the first valid period has elapsed after the operation of not accepting the payment (the operation that is the source of the payment cancellation notice in S55 of FIG. 11) is accepted in the first payment application 20-1 (S54 (processing after the second time) in FIG. 11). In addition, the payment server 100 acquires store input information from the store payment terminal 30, transmits payment information to the first payment application 20-1 that is the sender of the tag ID, and transmits payment information to the second payment application 20 if the tag ID is received from the second payment application 20-2 after the first valid period has elapsed after the operation of not accepting the payment is accepted in the first payment application 20-1. FIG. 13 is a diagram showing an example of the second scene realized by the payment server 100. When an operation not to accept the payment is performed in the first payment application 20-1, the first payment application 20-1 transmits a payment cancellation notice to the payment server 100. After that, when the second payment application 20-2 reads the tag ID and transmits it to the payment server 100 within the first valid period after the store input information is input, the payment server 100 transmits the payment information to the second payment application 20-2. In response to this, the second payment application 20-2 displays a screen for NFC payment. Note that, when the first payment application 20-1 is set not to transmit a payment cancellation notice to the payment server 100, when the second payment application 20-2 reads the tag ID and transmits it to the payment server 100, the payment server 100 may transmit the payment information to the second payment application 20-2. Conversely, if the second payment application 20-2 reads the tag ID and transmits it to the payment server 100 after the first valid period has elapsed since the store input information was entered, the payment server 100 does not transmit the payment information to the second payment application 20-2. As a result, the second payment application 20-2 does not display a screen for NFC payment, but displays another screen.13 is a scene in which a user (for example, by mistake) reads a tag ID with a first payment application 20-1 and transmits it to the payment server 100, and then another user reads a tag ID with a second payment application 20-2 and transmits it to the payment server 100, or a user who owns multiple user terminal devices 10 reads a tag ID with the payment application 20-1 of a first user terminal device 10-1 and transmits it to the payment server 100, and then reads a tag ID with the payment application 20-2 of another second user terminal device 10-2 and transmits it to the payment server 100. According to the present embodiment, even in these cases, the payment can be made by a payment application 20 that is highly likely to be the original payer, and appropriate measures can be taken.

[0060] Furthermore, when the payment server 100 receives tag IDs from multiple application programs before acquiring store input information from the store payment terminal 30, the payment server 100 transmits payment information to the application program that transmitted the last received tag ID, on condition that the time from the reception timing of the last received tag ID to the acquisition timing of the store input information is within the second validity period. FIG. 14 is a diagram showing an example of a third scene realized by the payment server 100. Before the store input information is input to the store payment terminal 30, the first payment application 20-1 reads the tag ID and transmits it to the payment server 100, and then the second payment application 20-2 reads the tag ID and transmits it to the payment server 100. If the store input information is acquired from the store terminal device 30 within the second validity period after acquiring the tag ID from the second payment application 20-2, the payment server 100 transmits payment information to the second payment application 20-2 that last transmitted the tag ID. In response to this, the second payment application 20-2 displays a screen for NFC payment. The scene shown in FIG. 14 may also occur for the same reason as that described in FIG. 13. According to this embodiment, it is possible to appropriately deal with these events.

[0061] In the scene of FIG. 13, the payment server 100 may acquire store input information from the store payment terminal 30, transmit the payment information to the first payment application 20-1 that is the sender of the tag ID, and then transmit the payment information to the first payment application 20-1 again if the tag ID is received again from the first payment application 20-1 before the first validity period has elapsed. In this scene, the first payment application 20-1 may transition to a state in which the tag ID is read when an operation to not accept the payment is received, for example. In this case, the first payment application 20-1 may not transmit a payment cancellation notice to the payment server 100 when an operation to not accept the payment is performed. Conversely, the first payment application 20-1 may transmit a payment cancellation notice to the payment server 100 when an operation to not accept the payment is performed. In this case, the payment server 100 may set the receipt of the payment cancellation notice as a condition for transmitting the payment information again (regardless of whether it is the same payment application 20 or not). This allows the user to smoothly resume electronic payment even if, for example, the user mistakenly performs an operation that does not approve the payment.

[0062] Here, in order to allow the user or a store clerk to confirm that it is within the second validity period, the store payment terminal 30 may be configured to notify whether it is within the second validity period. For example, the payment server 100 may communicate with the store payment terminal 30 to display the remaining time of the second validity period on the display unit of the store payment terminal 30, or may turn on a lamp on the store payment terminal 30 (for example, turned on: within the second validity period, turned off: the second validity period has elapsed).

[0063] According to the embodiment described above, it is possible to practically improve the convenience of electronic payment.

[0064] The above describes the form for carrying out the present invention using an embodiment, but the present invention is not limited to such an embodiment, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present invention. [Explanation of symbols]

[0065] E. Store Facilities M medium S Payment System 10 User terminal device 20. Payment App 30 Store payment terminal 40 Store code image 60 Payment Cards 70 Credit card processing terminal 80 NFC Tags 100 Payment Server 170 Storage section 176 Tag ID Mapping Information 200 Credit Card Server

Claims

1. A payment system including a user terminal device having a near field communication (NFC) function and a payment server that communicates with the user terminal device, The user terminal device When acquiring a tag ID from an NFC tag that is installed in a store and that stores a tag ID that can identify at least a part of the store, the store payment terminal installed in the store, and the affiliated store to which the store belongs, by the NFC function, transmitting the tag ID to the payment server; The payment server, Obtaining store input information related to payment from the store payment terminal, and receiving the store input information and payment information corresponding to the tag ID received from the user terminal device, (1) Refer to correspondence information between the tag ID and information capable of recognizing the store payment terminal stored in the storage unit, and obtain the tag ID from the store input information from the store payment terminal corresponding to the tag ID in the correspondence information, or (2) obtaining the store input information based on the time relationship between the time when the tag ID was received and the time when the store input information was obtained, and based on the positional relationship between the user terminal device and the store; Transmitting the acquired payment information to the user terminal device that is the source of the tag ID; The user terminal device Displaying the payment information and accepting a payment approval operation by the user; The payment server starts counting a first validity period based on the time when the store input information is acquired from the store payment terminal, and invalidates the payment related to the store input information when the first validity period has elapsed. Payment system.

2. the payment server transmits the payment information to a first user terminal device that is a sender of the tag ID, and when the payment server receives the tag ID from a second user terminal device before the first validity period has elapsed after an operation of not accepting the payment is accepted in the first user terminal device, transmits the payment information to the second user terminal device; The payment system according to claim 1.

3. the payment server transmits the payment information to a first user terminal device that is a sender of the tag ID, and when the payment server receives the tag ID again from the first user terminal device before the first validity period has elapsed, transmits the payment information again to the first user terminal device; The payment system according to claim 1.

4. the payment server transmits the payment information to a first user terminal device that is a transmission source of the tag ID, and when the payment server receives the tag ID from the second user terminal device after the first validity period has elapsed after an operation of not accepting the payment is accepted in the first user terminal device, the payment server does not transmit the payment information to the second user terminal device; The payment system according to claim 2.

5. when the payment server receives the tag IDs from a plurality of user terminal devices before acquiring the store input information from the store payment terminal, the payment server transmits the payment information to the user terminal device that is a source of the last received tag ID, on condition that the time from the reception timing of the last received tag ID to the acquisition timing of the store input information is within a second validity period. The payment system according to claim 1.

6. The second validity period is shorter than the first validity period. The payment system according to claim 5.

7. The NFC tag is an independent NFC tag that is not an internal function of the store payment terminal. A payment system according to any one of claims 1 to 6.

8. The payment system is capable of performing a payment by reading information from a code image installed in a store, in addition to the payment using the NFC function, In the user terminal device, the number of operations required to complete a payment when the tag ID is acquired by the NFC function is smaller than the number of operations required to manually start an application program running on the user terminal device and then perform a payment using the code image; A payment system according to any one of claims 1 to 6.

9. The tag ID is information that can identify the store payment terminal, and is ID information that is assigned in advance to at least a part of the store, the store payment terminal installed in the store, and the affiliated store to which the store belongs. A payment system according to any one of claims 1 to 6.

10. The tag ID is any ID information, The information that can identify the store payment terminal includes at least a portion of the store, the store payment terminal installed in the store, and the affiliated store to which the store belongs. A payment system according to any one of claims 1 to 6.

11. A payment system comprising a user terminal device having a near field communication (NFC) function and a payment server communicating with the user terminal device, The user terminal device When acquiring a tag ID from an NFC tag that is installed in a store and that stores a tag ID that can identify at least a part of the store, the store payment terminal installed in the store, and the affiliated store to which the store belongs, by the NFC function, transmitting the tag ID to the payment server; The payment server, Obtaining store input information related to payment from the store payment terminal, and receiving the store input information and payment information corresponding to the tag ID received from the user terminal device, (1) Refer to correspondence information between the tag ID and information capable of recognizing the store payment terminal stored in the storage unit, and obtain the tag ID from the store input information from the store payment terminal corresponding to the tag ID in the correspondence information, or (2) obtaining the store input information based on the time relationship between the time when the tag ID was received and the time when the store input information was obtained, and based on the positional relationship between the user terminal device and the store; Transmitting the acquired payment information to the user terminal device that is the source of the tag ID; The user terminal device Displaying the payment information and accepting a payment approval operation by the user; the payment server transmits the payment information to a first user terminal device that is a transmission source of the tag ID, and when the payment server receives the tag ID from a second user terminal device after an operation of accepting the payment is accepted in the first user terminal device, does not transmit the payment information to the second user terminal device; Payment system.

12. A payment system comprising a user terminal device having a near field communication (NFC) function and a payment server communicating with the user terminal device, The user terminal device When acquiring a tag ID from an NFC tag that is installed in a store and that stores a tag ID that can identify at least a part of the store, the store payment terminal installed in the store, and the affiliated store to which the store belongs, by the NFC function, transmitting the tag ID to the payment server; The payment server, Obtaining store input information related to payment from the store payment terminal, and receiving the store input information and payment information corresponding to the tag ID received from the user terminal device, (1) Refer to correspondence information between the tag ID and information capable of recognizing the store payment terminal stored in the storage unit, and obtain the tag ID from the store input information from the store payment terminal corresponding to the tag ID in the correspondence information, or (2) obtaining the store input information based on the time relationship between the time when the tag ID was received and the time when the store input information was obtained, and based on the positional relationship between the user terminal device and the store; Transmitting the acquired payment information to the user terminal device that is the source of the tag ID; The user terminal device Displaying the payment information and accepting a payment approval operation by the user; when the payment server receives the tag IDs from a plurality of user terminal devices before acquiring the store input information from the store payment terminal, the payment server transmits the payment information to the user terminal device that is a source of the last received tag ID, on condition that the time from the reception timing of the last received tag ID to the acquisition timing of the store input information is within a second validity period. Payment system.

13. A payment server that configures a payment system by communicating with a user terminal device having a Near Field Communication (NFC) function, from the user terminal device, an NFC tag that is installed in a store and stores a tag ID that can identify at least a part of the store, the store payment terminal installed in the store, and the affiliated store to which the store belongs, the tag ID is acquired by the NFC function; Obtaining store input information related to payment from the store payment terminal, and receiving the store input information and payment information corresponding to the tag ID received from the user terminal device, (1) Refer to correspondence information between the tag ID and information capable of recognizing the store payment terminal stored in the storage unit, and obtain the tag ID from the store input information from the store payment terminal corresponding to the tag ID in the correspondence information, or (2) obtaining the store input information based on the time relationship between the time when the tag ID was received and the time when the store input information was obtained, and based on the positional relationship between the user terminal device and the store; Transmitting the acquired payment information to the user terminal device that is the sender of the tag ID, and causing the user terminal device to display the payment information and accept an operation of payment approval by the user; a count of a first valid period is started based on a point in time when the store input information is acquired from the store payment terminal, and when the first valid period has elapsed, the payment related to the store input information is invalidated; Payment server.

14. A payment system including a user terminal device having a near field communication (NFC) function and a payment server that communicates with the user terminal device, The user terminal device, When a tag ID is acquired by the NFC function from an NFC tag that is installed in a store and that stores a tag ID that can identify at least a part of the store, the store payment terminal installed in the store, and the affiliated store to which the store belongs, the tag ID is transmitted to the payment server; The payment server, Obtaining store input information related to payment from the store payment terminal, and receiving the store input information and payment information corresponding to the tag ID received from the user terminal device, (1) Refer to correspondence information between the tag ID and information capable of recognizing the store payment terminal stored in the storage unit, and obtain the tag ID from the store input information from the store payment terminal corresponding to the tag ID in the correspondence information, or (2) obtaining the store input information based on the time relationship between the time when the tag ID was received and the time when the store input information was obtained, and based on the positional relationship between the user terminal device and the store; Transmitting the acquired payment information to the user terminal device that is the source of the tag ID; The user terminal device, Displaying the payment information and accepting a payment approval operation by the user; The payment server starts counting a first validity period based on a point in time when the store input information is acquired from the store payment terminal, and invalidates the payment related to the store input information when the first validity period has elapsed. Payment method.

15. A payment server that configures a payment system by communicating with a user terminal device having a Near Field Communication (NFC) function, from the user terminal device, acquiring the tag ID acquired by the NFC function from an NFC tag that is installed in a store and stores a tag ID that can identify at least a part of the store, the store payment terminal installed in the store, and the affiliated store to which the store belongs; Obtaining store input information related to payment from the store payment terminal, and receiving the store input information and payment information corresponding to the tag ID received from the user terminal device, (1) Refer to correspondence information between the tag ID and information capable of recognizing the store payment terminal stored in the storage unit, and obtain the tag ID from the store input information from the store payment terminal corresponding to the tag ID in the correspondence information, or (2) obtaining the store input information based on the time relationship between the time when the tag ID was received and the time when the store input information was obtained, and based on the positional relationship between the user terminal device and the store; Transmitting the acquired payment information to the user terminal device that is the sender of the tag ID, and causing the user terminal device to display the payment information and accept an operation of payment approval by the user; a count of a first valid period is started based on a point in time when the store input information is acquired from the store payment terminal, and when the first valid period has elapsed, the payment related to the store input information is invalidated; Payment method.

16. A payment server constituting a payment system by communicating with a user terminal device having a near field communication (NFC) function, from the user terminal device, an NFC tag that is installed in a store and stores a tag ID that can identify at least a part of the store, the store payment terminal installed in the store, and the affiliated store to which the store belongs, the tag ID is acquired by the NFC function; Obtaining store input information related to payment from the store payment terminal, and receiving the store input information and payment information corresponding to the tag ID received from the user terminal device, (1) Refer to correspondence information between the tag ID and information capable of recognizing the store payment terminal stored in the storage unit, and obtain the tag ID from the store input information from the store payment terminal corresponding to the tag ID in the correspondence information, or (2) obtaining the store input information based on the time relationship between the time when the tag ID was received and the time when the store input information was obtained, and based on the positional relationship between the user terminal device and the store; Transmitting the acquired payment information to the user terminal device that is the sender of the tag ID, and causing the user terminal device to display the payment information and accept an operation of payment approval by the user; sending the payment information to a first user terminal device which is a sender of the tag ID, and when the tag ID is received from a second user terminal device after an operation of accepting the payment is accepted in the first user terminal device, not sending the payment information to the second user terminal device; Payment server.

17. A payment system comprising a user terminal device having a near field communication (NFC) function and a payment server communicating with the user terminal device, The user terminal device, When a tag ID is acquired by the NFC function from an NFC tag that is installed in a store and that stores a tag ID that can identify at least a part of the store, the store payment terminal installed in the store, and the affiliated store to which the store belongs, the tag ID is transmitted to the payment server; The payment server, Obtaining store input information related to payment from the store payment terminal, and receiving the store input information and payment information corresponding to the tag ID received from the user terminal device, (1) Refer to correspondence information between the tag ID and information capable of recognizing the store payment terminal stored in the storage unit, and obtain the tag ID from the store input information from the store payment terminal corresponding to the tag ID in the correspondence information, or (2) obtaining the store input information based on the time relationship between the time when the tag ID was received and the time when the store input information was obtained, and based on the positional relationship between the user terminal device and the store; Transmitting the acquired payment information to the user terminal device that is the source of the tag ID; The user terminal device, Displaying the payment information and accepting a payment approval operation by the user; The payment server, sending the payment information to a first user terminal device which is a sender of the tag ID, and when the tag ID is received from a second user terminal device after an operation of accepting the payment is accepted in the first user terminal device, not sending the payment information to the second user terminal device; Payment method.

18. A payment server constituting a payment system by communicating with a user terminal device having an NFC (Near Field Communication) function, from the user terminal device, acquiring the tag ID acquired by the NFC function from an NFC tag that is installed in a store and stores a tag ID that can identify at least a part of the store, the store payment terminal installed in the store, and the affiliated store to which the store belongs; Obtaining store input information related to payment from the store payment terminal, and receiving the store input information and payment information corresponding to the tag ID received from the user terminal device, (1) Refer to correspondence information between the tag ID and information capable of recognizing the store payment terminal stored in the storage unit, and obtain the tag ID from the store input information from the store payment terminal corresponding to the tag ID in the correspondence information, or (2) obtaining the store input information based on the time relationship between the time when the tag ID was received and the time when the store input information was obtained, and based on the positional relationship between the user terminal device and the store; Transmitting the acquired payment information to the user terminal device that is the sender of the tag ID, and causing the user terminal device to display the payment information and accept an operation of payment approval by the user; sending the payment information to a first user terminal device which is a sender of the tag ID, and when the tag ID is received from a second user terminal device after an operation of accepting the payment is accepted in the first user terminal device, not sending the payment information to the second user terminal device; Payment method.

19. A payment server constituting a payment system by communicating with a user terminal device having a near field communication (NFC) function, from the user terminal device, an NFC tag that is installed in a store and stores a tag ID that can identify at least a part of the store, the store payment terminal installed in the store, and the affiliated store to which the store belongs, the tag ID is acquired by the NFC function; Obtaining store input information related to payment from the store payment terminal, and receiving the store input information and payment information corresponding to the tag ID received from the user terminal device, (1) Refer to correspondence information between the tag ID and information capable of recognizing the store payment terminal stored in the storage unit, and obtain the tag ID from the store input information from the store payment terminal corresponding to the tag ID in the correspondence information, or (2) obtaining the store input information based on the time relationship between the time when the tag ID was received and the time when the store input information was obtained, and based on the positional relationship between the user terminal device and the store; Transmitting the acquired payment information to the user terminal device that is the sender of the tag ID, and causing the user terminal device to display the payment information and accept an operation of payment approval by the user; When the tag IDs are received from a plurality of user terminal devices before the store input information is acquired from the store payment terminal, the payment information is transmitted to the user terminal device that is the source of the last received tag ID, on condition that the time from the reception timing of the last received tag ID to the acquisition timing of the store input information is within a second validity period. Payment server.

20. A payment system comprising a user terminal device having a near field communication (NFC) function and a payment server communicating with the user terminal device, The user terminal device, When a tag ID is acquired by the NFC function from an NFC tag that is installed in a store and that stores a tag ID that can identify at least a part of the store, the store payment terminal installed in the store, and the affiliated store to which the store belongs, the tag ID is transmitted to the payment server; The payment server, Obtaining store input information related to payment from the store payment terminal, and receiving the store input information and payment information corresponding to the tag ID received from the user terminal device, (1) Refer to correspondence information between the tag ID and information capable of recognizing the store payment terminal stored in the storage unit, and obtain the tag ID from the store input information from the store payment terminal corresponding to the tag ID in the correspondence information, or (2) obtaining the store input information based on the time relationship between the time when the tag ID was received and the time when the store input information was obtained, and based on the positional relationship between the user terminal device and the store; Transmitting the acquired payment information to the user terminal device that is the source of the tag ID; The user terminal device, Displaying the payment information and accepting a payment approval operation by the user; When the payment server receives the tag IDs from a plurality of user terminal devices before acquiring the store input information from the store payment terminal, the payment server transmits the payment information to the user terminal device that is the source of the last received tag ID, on condition that the time from the reception timing of the last received tag ID to the acquisition timing of the store input information is within a second validity period. Payment method.

21. A payment server constituting a payment system by communicating with a user terminal device having an NFC (Near Field Communication) function, from the user terminal device, acquiring the tag ID acquired by the NFC function from an NFC tag that is installed in a store and stores a tag ID that can identify at least a part of the store, the store payment terminal installed in the store, and the affiliated store to which the store belongs; Obtaining store input information related to payment from the store payment terminal, and receiving the store input information and payment information corresponding to the tag ID received from the user terminal device, (1) Refer to correspondence information between the tag ID and information capable of recognizing the store payment terminal stored in the storage unit, and obtain the tag ID from the store input information from the store payment terminal corresponding to the tag ID in the correspondence information, or (2) obtaining the store input information based on the time relationship between the time when the tag ID was received and the time when the store input information was obtained, and based on the positional relationship between the user terminal device and the store; Transmitting the acquired payment information to the user terminal device that is the sender of the tag ID, and causing the user terminal device to display the payment information and accept an operation of payment approval by the user; When the tag IDs are received from a plurality of user terminal devices before the store input information is acquired from the store payment terminal, the payment information is transmitted to the user terminal device that is the source of the last received tag ID, on condition that the time from the reception timing of the last received tag ID to the acquisition timing of the store input information is within a second validity period. Payment method.

Images