Settlement system, settlement method, and application program

Abstract

To actually improve the convenience of electronic settlement.SOLUTION: A settlement system including an application program that operates in a customer terminal having an NFC function and a settlement server that communicates with the application program, the application program causing the customer terminal to transmit a tag ID to the settlement server when the tag ID is acquired by the NFC function from an NFC tag that is installed in a shop and stores the tag ID capable of recognizing at least a part of the shop, shop settlement terminals installed in the shop, and affiliated shops to which the shop belongs, in the settlement system, the settlement server transmits the settlement information corresponding to the tag ID received from the application program to the application program, and the application program causes the utilizer terminal to display the settlement information and accept an operation of settlement approval by the utilizer.SELECTED DRAWING: Figure 8

Description

[Technical Field]

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

[0002] Conventionally, electronic payment services that involve the exchange of information between terminal devices such as smartphones and store facilities have become widespread. The practical application of NFC (Near Field Communication) for this information exchange is also progressing. In relation to this, Patent Document 1 describes the use of NFC functionality in store payment terminals to enable contactless credit card payments. [Prior art documents] [Patent documents]

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

[0004] However, while electronic payment services are often conducted via point-of-sale (POS) devices installed in stores, it is difficult to equip all POS devices with NFC functionality in a widespread electronic payment service. As such, conventional technologies have not always been able to realistically improve the convenience of electronic payments.

[0005] The present invention has been made in consideration of these circumstances, and one of its objects is to provide a payment system, a payment method, and an application program that can realistically improve the convenience of electronic payments. [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 that communicates with the application program, wherein the application program causes the user terminal device to transmit 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 identify 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 application program causes the user terminal device to transmit the tag ID to the payment server, 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. [Effects of the Invention]

[0007] According to one aspect of the present invention, it is possible to practically improve the convenience of electronic payments. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 illustrates basic aspects of brick-and-mortar electronic payment. [Figure 2] FIG. 1 is a diagram illustrating an example of a configuration for performing electronic payment (terminal payment) using a payment application. [Figure 3] FIG. 10 is a diagram showing an example of the contents of user information 172. [Figure 4] FIG. 10 is a diagram showing an example of the contents of affiliated store / shop information 174. [Figure 5] FIG. 10 is a diagram showing an outline of a processing flow when a user scan is performed. [Figure 6] FIG. 10 is a diagram showing an outline of the processing 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-input type NFC payment. [Figure 9] FIG. 10 is a sequence diagram showing an example of the processing flow of store-entry-type NFC payment. [Figure 10] FIG. 10 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] FIG. 1 is a diagram illustrating a user-input type NFC payment. [Figure 12] FIG. 10 is a sequence diagram showing an example of the processing flow of a user-input type NFC payment. [Figure 13] FIG. 10 is a diagram showing an example of screen transitions of the payment application 20 when a user-input type NFC payment is made. DETAILED DESCRIPTION OF THE INVENTION

[0009] [overview] Hereinafter, with reference to the drawings, embodiments 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 will be referred to as a payment app. The combination of the payment server and the credit card server may also be referred to as a payment management system. An electronic payment service is a service that supports payments for the purchase of goods and services at a store. A store is, for example, a physical store (real store) existing in real space, but may also include a virtual store for e-commerce transactions. A virtual store may also include a store operated by an entity other than the operator of the electronic payment service. In such a case, when paying for purchases at the virtual store, the user is controlled to transition to the interface screen of the electronic payment service. In an electronic payment service, a store is treated as belonging to, for example, an affiliated store (brand), and when a purchase is made at a store, processing such as payment is primarily conducted between the user and the affiliated store. Alternatively, processing such as payment may be conducted between the user and the store.

[0010] [Electronic payment methods at brick-and-mortar stores] FIG. 1 illustrates the basic aspects of brick-and-mortar electronic payments. Electronic payments are generally carried out by three parties: a medium M held by a user U, store equipment E, and a payment system S. The medium M may be a portable computer device such as a smartphone or a credit card. The store equipment E resides in a physical store (hereinafter simply referred to as the store) in real space and may include a POS device, a wireless communication device, a credit card reader, a printed code image such as a QR Code (registered trademark), or a display device displaying the code image. In brick-and-mortar electronic payments, information that can identify the user and information about the payment amount are first shared unidirectionally or bidirectionally between the medium M and the store equipment E. At this time, either the medium M or the store equipment E optically reads various information from a code image displayed by the other, provides information via near-field communication (NFC), or reads the PAN (primary account number) using a credit card reader. Then, either the medium M or the store equipment E (the party that obtains information from the other) transmits the payment information required for the payment to the payment system S via a network NW. Both the medium M and the store equipment E may send some information to the payment system S. The payment system S manages various information about the user U and performs electronic payments between the store and the user U in various ways. Electronic payments are performed using either or both of a prepaid system and a postpaid system, or by other methods. In addition, electronic payments may also include so-called online shopping, which is performed between 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. The various devices that communicate via the network NW, which will be described below, 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 the configuration for performing electronic payment (terminal payment) using a payment app. This electronic payment is performed mainly by a payment app 20 running on a user terminal device 10, which is one of the media M, one or more store payment terminals 30 and one or more store code images 40, which are one of the store facilities E, and a payment server 100, which constitutes part of a payment system S. 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 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, which operates in cooperation with the payment server 100 to provide electronic payment services to users. The payment application 20 is installed in the user terminal device 10 from, for example, 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) that has 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 paper or plastic medium. 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 oversees the stores. In electronic payment services, customers who provide goods or services are treated as affiliated stores (brands), and one or more stores exist under the affiliated store. An affiliated store may operate only one store. The information terminal 50 is a smartphone, tablet terminal, personal computer, etc. An affiliated store interface 55 runs on the information terminal 50. The affiliated store interface 55 may be an affiliated store app or a web page displayed by a general-purpose browser. The affiliated store interface 55 accepts coupon settings and the like from the affiliated store operator and transmits them to the payment server 100. By executing the affiliated store interface 55, the information terminal 50 may have the function of displaying a code image corresponding to the store code image 40 or reading a code image displayed by the user terminal device 10 (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 management unit 120, a payment processing unit 130, and a storage unit 170. The components other than the storage 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 with a non-transitory storage medium) such as a hard disk drive (HDD) or flash memory, or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device.

[0017] The storage unit 170 is a hard disk drive (HDD), flash memory, RAM (Random Access Memory), or the like. The storage unit 170 may be a NAS (Network Attached Storage) 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 explained 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 to the user terminal device 10 in the form of a web page, and provides the user terminal device 10 with parameters required for the payment application 20 to render an image.

[0019] The information management unit 120 edits, adds, deletes, etc., user information 172 and affiliated store / shop information 174, and manages them.

[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 this 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 remittance processing between users. When registering for the electronic payment service, registration of a phone number and password is required. 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 the user has set by transferring money to the account in advance. Remittance methods include depositing money into an ATM (Automatic Teller Machine) of a designated service provider (bank) or transferring money 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 payments. The terminal payment method is setting information indicating whether the user will make electronic payment using the charge balance (balance payment) or by 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 by deferred payment in card payment. The various historical information includes charge history, which is a record of the user transferring money to the electronic payment service in advance to increase the charge balance, and payment history, which shows the details of the 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 ID document. Deferred payment can be selected if identity verification has been completed, and the user with account ID "002" in the figure has not completed identity verification and 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 settings have been completed to make deferred payment selectable. Deferred payment condition information is information indicating various conditions such as the deferred payment limit and the amount used for 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 ID is associated with an affiliated store name and sales amount (described above), and a third table 174C in which a store ID is associated with a store ID. In addition to this information, the affiliated store / store information 174 may also include information such as the category of the affiliated store or store, the store's location, and payment patterns. As shown in the figure, the third table 174C may further associate, for each store, the identification information (device ID) of the store payment terminal 30 in the 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 explained below.

[0025] FIG. 5 shows an overview 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 using its optical reading function (S1). The store code image 40 includes store URL information. The payment application 20 sends 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 information about the affiliated store name and store name (S3), and sends this to the payment application 20 (S4). The user enters the payment amount into the payment application 20 on the screen displaying the affiliated store name and store name (S5). The payment application 20 then generates second payment information including at least the payment amount and sends 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 proceeds. The item value of the affiliated store's sales proceeds is not used as electronic money itself, for example, but rather the amount corresponding to the item value of the sales proceeds is transferred to a bank account in a cycle determined by an agreement between the affiliated store and the electronic payment service. On the other hand, if the "Terminal Payment Method" is set to "Deferred Payment," 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 user's monthly usage amount 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 app 20 via the content providing unit 110 (S8), and the payment app 20 displays the payment completion screen (S9). When the store code image 40 is displayed on a display installed in the store, the store code image 40 may include information on the payment amount in addition to the store URL. In this case, the procedure for the user to input 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 overview of the processing flow when a store scan is performed. First, when the payment app 20 is launched, when a payment operation is performed using the payment app 20, when an automatic update timing (e.g., every minute) occurs, and at other timings, the payment app 20 sends a request to issue 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 sends it to the payment app 20 (S13). The payment app 20 displays a code image, such as a QR code or 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 using its optical reading function to obtain the one-time code, etc. (S15). The store payment terminal 30 then generates payment information including the one-time code, payment amount, affiliated store ID, store ID, etc., and sends it to the payment server 100 (S16). The payment amount information is acquired in advance by reading a barcode or manually entering it.

[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," it performs electronic payment based on the received second payment information (S17-1). The processing content at this time is the same as the processing of S7-1 in FIG. 5. On the other hand, if the "terminal payment method" is set to "post-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, issuing a one-time code may be omitted in store scanning, 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] It should be noted that the "post-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 using 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, which constitutes part of a payment system S, and a credit card server 200. 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 in-store payment terminal 30. The credit processing terminal 70 includes, for example, a credit card reader and a POS device. The credit card terminal reads a personal identification number (PIN) from an inserted or held-up credit card and compares it with the PIN entered by the user. It also transmits a primary account number (PAN) read from the credit card to the credit card server 200 via the POS device. The POS device cooperates with the credit card terminal to transmit information such as the payment amount to the credit card server 200. A payment agent (acquirer) server may be interposed between the credit card processing terminal 70 and the credit card server 200; however, for simplicity, the following description omits the server. The payment card 60 is, for example, similar to a commonly used credit card, with a communication chip embedded in the card substrate. The communication chip incorporates a storage medium storing 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 (messages) sent and received when using a credit card include 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 a network NW. The credit card server 200 includes, for example, an information management unit 210, a credit interface 220, a payment allocation unit 230, a credit payment processing unit 240, and a memory unit 270. The components other than the memory unit 270 are implemented by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be implemented by hardware (including circuitry) such as an LSI, ASIC, FPGA, or GPU, or may be implemented by a combination of software and hardware. The program may be stored in advance in a storage device such as an HDD or flash memory (a storage device with a non-transitory storage medium), or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device. The memory unit 270 stores information such as card user information 272.

[0036] The information management unit 210 edits, adds, deletes, etc., and manages the card user information 272. 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 one another. The card payment method is setting information that indicates whether the user will make electronic payment using the charged balance (balance payment) or deferred payment when making a 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 the company, and if it is a code for the company, passes the message received from the credit processing terminal 70 to the payment allocation unit 230, and if it is not a code for the company, discards the received message.

[0038] The payment allocating unit 230 refers to the card user information 272 of the user corresponding to the message obtained from the credit interface 220, and determines whether the "card payment method" is set to "post-payment." If the "card payment method" is set to "post-payment," the payment allocating unit 230 notifies the credit interface 220 of this 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 allocating unit 230 adds the user's account ID to the message obtained from the credit interface 220 and sends it to the payment server 100, requesting electronic payment. When requested to make electronic payment, the payment server 100 performs the same processes as S7-1 in Figure 5 and S17-1 in Figure 6.

[0039] The credit interface 220 checks the PAN and expiration date, and verifies whether the cumulative payment amount exceeds the current month's upper limit, 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] In addition to the terminal payment and card payment described above, the payment system can also perform payments using NFC (hereinafter referred to as NFC payment). This will be explained below. Note that the payment system may also be one that exclusively performs NFC payments. There may be two NFC payment methods, the first method (store input type) and the second method (user input type), which will be described below, but the payment system may only support one of them.

[0041] (Store input type) FIG. 8 is a diagram illustrating a store-input NFC payment. In the store-input NFC payment, a store clerk T inputs the payment amount into the store payment terminal 30, which is a POS device, by scanning a barcode or manually entering the amount. The input information (input information) is transmitted to the payment server 100. An object with an NFC tag 80 built in or attached to it is placed near 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 tag that does not have its own power source and is configured to activate when powered by an external device and transmit information (tag ID) stored in its memory. When a user holds a user terminal device 10 with 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 some 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. The payment server 100 selects input information received from the store corresponding to the received tag ID and transmits payment information to the payment app 20 based on the input information. This allows the payment app 20 to obtain payment information without directly communicating with the store payment terminal 30 and accept the user's payment approval operation (such as pressing 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 payments can be improved in practice.

[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.). The ID information assigned to the store or affiliated store may be, for example, the device ID of the store payment terminal 30 (POS device). The ID information may also be the login ID of the affiliated store interface 55, or the affiliated store ID or store ID shown in FIG. 4. The ID information may also include multiple of the above. In this case, at the start of operation, a process is performed to rewrite the ID information in the NFC tag 80 using, for example, the information terminal 50. (2) The tag ID is arbitrary information (for example, the information remains as it was at the time the NFC tag 80 was purchased), and the tag ID mapping information 176 manages the correspondence between the tag ID and the store, store payment terminal 30, or 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 processing flow for store-input NFC payment. Here, it is assumed that the tag ID has already been associated with the store or affiliated store. First, input information is generated in the store terminal device 30 (S21). The store payment terminal 30 transmits the 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 processes of S21 and S22 and S23 may be performed in either order, but in terms of business practice, it is more natural for the user to hold the user terminal device 10 over the NFC tag 80 after the input information has been generated.

[0044] Next, the user terminal device 10 (payment application 20) transmits information including the tag ID to the payment server 100 (S24). The payment processing unit 130 of the payment server 100, for example, 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 information about the store or affiliated store, and may further include the date and time of payment, points awarded, campaign information, etc. If the tag ID includes information associated with a device ID in the tag ID mapping information 176 or a device ID, the store or affiliated store can be identified by referencing the third table 174C. Furthermore, if the tag ID is information associated with a device ID in the tag ID mapping information 176 or a 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 information associated with the device ID in the tag ID mapping information 176 or the device ID, the payment amount may be determined 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 being 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 payment processing (S29). This payment processing may be performed according to the user's "terminal payment method" setting, similar to the processing of S7-1 to S7-3 in FIG. 5 or the processing of S17-1 to S17-3 in FIG. 6. Upon completion of the payment processing, 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 information terminal 50 (S30, 31).

[0046] FIG. 10 is a diagram showing an example of the screen transitions of the payment app 20 when a store-input 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 has 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, processing up to S26 in FIG. 9 has been completed. Screen IM2 has a button B2 for accepting a payment acceptance 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 app 20, and when button B3 is operated, screen IM4, a payment completion notification screen similar to that when terminal payment is made as 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 an 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: launching payment application 20, issuing a scan instruction, and accepting payment. Therefore, the number of operations required to complete an NFC payment is fewer than the number of operations required to perform terminal payment, allowing the user to complete the payment with fewer operations. As a result, user convenience can be improved.

[0049] (User input type) User-input NFC payment will be described below. User-input NFC payment is similar in form to the user scan in FIG. 5. FIG. 11 is a diagram schematically illustrating user-input NFC payment. In user-input NFC payment, a user inputs the payment amount into payment application 20. The input information (input information) is sent to payment server 100. An object with an NFC tag 80 built in or with an NFC tag 80 attached is placed at an arbitrary location in the store (for example, around the cash register) (alternatively, the NFC tag 80 may be attached to a cash register, etc.). When a user holds a user terminal device 10 with 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 payment server 100 transmits information about the store or affiliated store identified based on the tag ID to payment application 20. The payment app displays information about the store or affiliated store and accepts the user's input of the payment amount. The user shows the payment screen displaying the payment amount to store clerk T, and then accepts the user's operation to approve the payment, completing the NFC payment. This type of payment can also be realized even if the store payment terminal 30 does not support NFC. As a result, it is possible to practically improve the convenience of electronic payments. The method of associating tag IDs with stores or affiliated stores is as described above.

[0050] FIG. 12 is a sequence diagram showing an example of the processing flow for user-input NFC payment. Here, it is assumed that the tag ID has already been associated with the store or affiliated store. First, 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 (S41). Next, the user terminal device 10 (payment application 20) transmits information including the tag ID to the payment server 100 (S42). For example, the payment processing unit 130 of the payment server 100 identifies the store or affiliated store from the tag ID (S43), and transmits information about the identified store or affiliated store to the payment application 20 (S44).

[0051] Upon receiving the store or affiliated store information, the payment application 20 accepts the input of the payment amount and (after confirmation by store clerk T) the operation of accepting the payment (S45), and once the operation is performed, sends a payment OK notification to the payment server 100 (S46). The payment processing unit 130 of the payment server 100 performs payment processing (S47). This payment processing may be performed according to the user's "terminal payment method" setting, similar to the processing of S7-1 to S7-3 in FIG. 5 or the processing of S17-1 to S17-3 in FIG. 6. Upon completion of the payment processing, the payment processing unit 130 of the payment server 100 sends a payment completion notification to the payment application 20 and the information terminal 50 (S48, S49).

[0052] FIG. 13 is a diagram showing an example of the screen transition of the payment app 20 when a user-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 has a button B1 for accepting an operation to proceed with the NFC payment. When button B1 is operated, screen IM5 is displayed. Note that depending on the type of OS 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 IM5 is displayed.

[0053] Screen IM5 includes an area A3 for inputting the payment amount. At this point, the processing up to S44 in FIG. 12 has been completed. Screen IM5 has a button B4 for accepting the payment approval operation. When button B4 is operated, screen IM3 is displayed. Subsequent screen transitions are the same as for the store input type.

[0054] Even with user-input NFC payment, the number of operations required to complete payment is, for example, one or two operations plus the input of the payment amount, as shown in FIG. 13. In contrast, the operations required to perform terminal payment (user scan) include at least three operations: launching payment application 20, issuing a scan instruction, and accepting payment, and both require the input of the payment amount. Therefore, the number of operations required to complete NFC payment is fewer than the number of operations required to perform terminal payment, allowing the user to complete the payment with fewer operations. As a result, user convenience can be improved.

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

[0056] 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]

[0057] E. Store Facilities M medium S payment system 10 User terminal device 20. Payment App 30 Store payment terminals 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 comprising an application program that runs on a user terminal device having an NFC (Near Field Communication) function, and a payment server that communicates with the application program, The application program is installed in 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 transmits payment information corresponding to the tag ID received from the application program to the application program; The application program is installed in the user terminal device. Displaying the payment information and accepting a payment approval operation by the user. Payment system.

2. The payment server acquires input information related to payment input to the store payment terminal at the timing of receiving the tag ID from the store payment terminal, and transmits the payment information based on the input information to the application program. The payment system according to claim 1.

3. The NFC tag is an independent NFC tag that is not an internal function of the store payment terminal. The payment system according to claim 2.

4. A payment system comprising an application program that runs on a user terminal device having an NFC (near field communication) function, and a payment server that communicates with the application program, The application program is installed in 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 transmits to the application program information on the store or the affiliated store corresponding to the tag ID received from the application program; The application program is installed in the user terminal device. Displaying information about the store or the affiliated store and accepting input of payment information including a payment amount by a user; transmitting the payment information to the payment server; Payment system.

5. A payment system comprising an application program that runs on a user terminal device having an NFC (Near Field Communication) function, and a payment server that communicates with the application program, The application program is installed in 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 stores a tag ID that can identify the payment amount of a transaction that is to be electronically paid in the payment system, the tag ID is transmitted to the payment server; the payment server transmits payment information including the payment amount corresponding to the tag ID received from the application program to the application program; The application program is installed in the user terminal device. Displaying the payment information and accepting a payment approval operation by the user. Payment system.

6. The payment system is capable of performing a payment by reading information from a code image installed in a store, separate from the payment using the NFC function, In the application program, 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 the application program and then perform a payment using the code image; A payment system according to any one of claims 1 to 5.

7. The tag ID is ID information that is assigned in advance to at least some 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 5.

8. The tag ID is any ID information, The payment server manages, in a storage unit, associations between the store, the store payment terminal installed in the store, and at least some of the affiliated stores to which the store belongs. A payment system according to any one of claims 1 to 5.

9. A payment system including an application program that runs on a user terminal device having an NFC (Near Field Communication) function and a payment server that communicates with the application program, The application program is installed on 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 transmits payment information corresponding to the tag ID received from the application program to the application program; The application program is installed on the user terminal device. Displaying the payment information and accepting a payment approval operation by the user. Payment method.

10. A payment system including an application program that runs on a user terminal device having an NFC (near field communication) function, and a payment server that communicates with the application program, The application program is installed on 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 transmits to the application program information on the store or the affiliated store corresponding to the tag ID received from the application program; The application program is installed on the user terminal device. Displaying information about the store or the affiliated store and accepting input of payment information including a payment amount by a user; transmitting the payment information to the payment server; Payment method.

11. A payment system including an application program that runs on a user terminal device having an NFC (Near Field Communication) function and a payment server that communicates with the application program, The application program is installed on 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 stores a tag ID that can identify the payment amount of a transaction that is to be electronically paid in the payment system, the tag ID is transmitted to the payment server; the payment server transmits payment information including the payment amount corresponding to the tag ID received from the application program to the application program; The application program is installed on the user terminal device. Displaying the payment information and accepting a payment approval operation by the user. Payment method.

12. An application program that operates on a user terminal device having an NFC (Near Field Communication) function and realizes a payment system by communicating with a payment server, 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 displays the payment information transmitted to the application program in accordance with the tag ID received from the application program, and accepts a payment approval operation by the user; Application program for.

13. An application program that operates on a user terminal device having an NFC (Near Field Communication) function and realizes a payment system by communicating with a payment server, 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 displays information about the store or the affiliated store transmitted to the application program corresponding to the tag ID received from the application program, and accepts input of payment information including a payment amount by the user; transmitting the payment information to the payment server; Application program for.

14. An application program that operates on a user terminal device having an NFC (Near Field Communication) function and realizes a payment system by communicating with a payment server, 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 stores a tag ID that can identify the payment amount of a transaction that is to be electronically paid in the payment system, the tag ID is transmitted to the payment server; the payment server displays payment information including the payment amount transmitted to the application program in accordance with the tag ID received from the application program, and accepts a payment approval operation by the user; Application program for.

Images