JP2015525383A - System and method for conducting transactions - Google Patents

Abstract

Embodiments of the present invention relate to systems, methods, processes, computer program code and means, etc. that perform payment transactions utilizing the near field electromagnetic communication (NFC) functionality of mobile devices.

Description

  The disclosed embodiments relate to systems and methods for conducting transactions and the like.

  Mobile devices such as smartphones have near field communication (NFC) functionality, and mobile devices are becoming able to communicate with readers, tags and other NFC devices using NFC. An NFC device is generally capable of operating in three modes of operation, such as “reader / writer”, “peer-to-peer” and “card emulation” modes. Various operation modes may be based on ISO / IEC 18092, 14443, NFC IP-1 standard, and the like.

  In the reader / writer mode, the NFC device can read an NFC Forum-managed tag type when reading an NFC Smart Poster tag. The reader / writer mode of the RF interface may conform to ISO / IEC14443 and FeliCa system. In peer-to-peer mode, two NFC devices can send and receive data (e.g., two devices can share Bluetooth or WiFi link setup parameters, or virtual Business cards (virtual business cards) or digital photos can be exchanged). Peer to peer mode may be based on ISO / IEC18092. In the card emulation mode, the NFC device looks almost the same as a conventional contactless smart card to an external reader. The card emulation mode allows contactless payment processing (contactless payment transactions) and ticketing processing (or ticket processing) by the NFC device without any changes to the existing payment processing infrastructure. Currently, many smartphones have an NFC function.

  Many mobile payment schemes require the NFC device to be used in “card emulation mode”. This mode allows the phone to function as a storage unit for securely encrypted payment card credentials. However, unfortunately, such a mode of use is based on a standard specification (or “method” where transaction card credentials are managed by a transaction card authority (e.g., Visa, American Express, etc.). )) And requires that a secure encryption chip called a “secure element” be present on the mobile device, which adds cost and complexity to the mobile device. . These encryption schemes are closed and exclusive, and licensing or usage is left to the discretion of the scheme owner. Licenses can be expensive and there is no guarantee that permission will be granted to entrants.

  Furthermore, the application processing required to execute the encryption scheme can be complicated. For example, one standard specification called “Globoplatform / JCOP” (which is essentially a Java runtime environment implemented on an NRC chip) is stored on the chip. Each payment card to be requested requires having its own Java application that manages the encryption and decryption of the card's data using a unique set of keys.

  The complexity of processing and security issues associated with managing various private key schemes has created a new instrument in the NFC payment ecosystem called the Trusted Service Manager (TSM). As a result. The TSM uses a plurality of encryption schemes for the customer's handset and has a job that functions as a reliable intermediary responsible for managing the movement of the credential information of the encrypted payment card. In particular, TSM exists because different associations have different schemes, and associations do not want to share their particular encryption and card management schemes with each other. Using TSM to store and manage payment cards on customer smartphones using card emulation mode NFC is expected to add cost equivalent to $ 5 per year.

  Using crypto card emulation mode NFC to make payments also creates an opportunity for handset manufacturers and wireless carriers to manage the process of placing payment cards on devices with chips that support NFC emulation mode. . Wireless carriers such as Verizon and ATT that work together as part of the Isis Consortium, and handset manufacturers such as Google, can have significant fees in the form of license fees or co-marketing fees. The payment card issuer is often asked to impose, and often does not ask the bank that is the primary issuer of the payment card. It is believed by the industry that ISS or Verizon is proposing that Isis is proposing that banks pay about $ 10 per transaction card each year to make payment cards available on NFC-enabled mobile phones.

  It would be desirable to provide methods and systems (including distribution and recovery proposals and distribution and collection of loyalty points and rewards) to solve these and other problems, using the mobile device's NFC functionality for payment transactions, etc. Yes. Other advantages and features will become more apparent upon understanding the following disclosure.

<Related applications>
This application includes US Provisional Patent Application No. 61 / 646,523, filed on May 14, 2012, and US Patent Application No. 13 / 768,156, filed on February 15, 2013, dated December 31, 2012. U.S. Patent Application No. 13 / 731,348, filed July 30, 2010, U.S. Patent Application No. 12 / 846,911, and U.S. Patent Application No. 13 / filed December 23, 2011. Enjoy the preferential benefits under 336,574, the entire contents of which are incorporated into this application's reference.

  An object of an embodiment in one aspect is to provide an improved method and system that uses the NFC function of a mobile device for payment transactions.

The system according to one embodiment comprises:
A transaction time information management device for identifying information related to a transaction, the transaction time information management device identifying a checkout token used for the transaction;
An NFC device that receives the checkout token from the transaction time information management device by communication with the transaction time information management device, wherein the checkout token is used in a mobile application of an NFC-compatible mobile device, An NFC device that wirelessly notifies an NFC reader of the NFC-compatible mobile device.

1 is a block diagram illustrating a system formed in connection with an embodiment. The flowchart which shows the process relevant to embodiment. 6 is a flowchart illustrating another process related to the embodiment.

  Embodiments of the present invention relate to systems, methods, processes, computer program code and means that utilize a near field communication (NFC) function of a mobile device for payment transactions. In general, embodiments may be deployed in systems such as those described in the above-assigned related applications, where such systems scan, capture, or enter codes associated with transactions. The mobile device is used to execute the transaction. A feature of one embodiment is that payments or other uses where the mobile device is used to perform transactions at a merchant location (or in one embodiment, an exchange in an automated teller machine, kiosk, interpersonal transaction, etc.) Described in connection with the trading system. In addition, embodiments may be used in connection with payment or other transaction systems, where the system generates or obtains a checkout token or other code, and the checkout token or code utilizes an NFC function. Mobile to start a transaction by providing it to another device involved in the transaction (e.g. merchant point-of-sale point of sale (POS) device, automated teller machine, kiosk, other personal device, etc.) The device is used.

  The features of the present invention are described assuming the use of a payment and transaction system as shown in the above related applications, and details of those systems themselves are not described in detail herein. However, embodiments of the present invention are not limited to examples used in connection with payment or transaction systems specifically described in related applications. Rather, utilizing the NFC functionality as described herein may be performed to enjoy desired results and benefits in a wide variety of payment or transaction systems, digital wallets, and the like. Further, although the embodiments are generally described herein in connection with transactions (e.g., payment transactions), embodiments may be used for other types such as loyalty, rewards or other proposed types of transactions, etc. May be used to obtain the desired result in a transaction, in which case one device (e.g. a mobile device) interacts with another device (e.g. another mobile device or a transaction place device) .

  FIG. 1 is a block diagram of a system 100 according to one embodiment, and features of the embodiment of the present invention will be described with reference to FIG. Further details of the system 100 are shown, for example, in related applications. As shown, a payment account owner (payment account holder), purchaser (buyer) or other user or operator (hereinafter referred to as `` customer '') is a mobile device 102 (e.g., mobile phone, etc.) Have or use. The mobile device 102 has a display screen (display screen) and a data input device (eg, keypad or touch screen). With respect to embodiments of the present invention, a customer uses a mobile device 102 to perform a transaction with a merchant or other entity (e.g., a bank) via a point of transaction device 106. It's okay. Transaction point information management device 106 is, for example, store point of sale terminal (point of sale terminal), automatic teller machine, other mobile devices (for example, portable POS terminal, other personal mobile devices, etc. ) Etc. The merchant may be a physical store, an e-commerce merchant, a mail order and telephone (MOTO) merchant, or another person or entity. In addition, the merchant need not be a `` merchant '' in the strict sense, but may be another person (in the case of transactions between individuals), such as an automated teller machine (ATM), etc. (Such as a kiosk) or other related device.

  For simplicity of explanation, devices associated with customers, customers, or other entities that act as buyers (or buyers) in transactions are referred to herein as “mobile device 102” or “NFC-enabled mobile device 102”. To be mentioned. Merchants, merchants, money receivers or other entities that function as sellers or money receivers in transactions are referred to as “transaction time information management device 106”. A person skilled in the art may be a conventional merchant store point-of-sale information management device (POS device) improved so that the transaction point-of-information management device 106 performs processing related to the present invention by understanding the present disclosure. Or it may be a device such as a mobile phone or other device (in one embodiment, the customer operates the mobile device and the merchant or other person participating in the transaction is also a mobile device) Will be allowed to operate).

  For one embodiment, the mobile device 102 is an NFC-enabled mobile such as a mobile phone with an installed radio frequency identification (RFID) chip (introduced as part of the mobile phone chipset or as an aftermarket SIM card). It is a mobile device compatible with the device 102. As a specific example, the mobile phone may be a Google Nexus S or a Blackberry 9600 smartphone, both of which incorporate an RFID chip. For one embodiment, mobile device 102 operates in accordance with one or more standards, such as ISO / IEC 18092, NFC IP-1, and ISO / IEC 14443 contactless communication standards.

  More specifically, for one embodiment, the mobile device 102 may operate in a so-called “reader / writer” mode, in which case the NFC device of the mobile device 102 is an NFC Forum compliant NFC tag (e.g., NFC It is possible to read data from the NFC tag of the device 104). In one embodiment, the mobile device 102 can also (or alternatively) operate in a so-called “peer-to-peer (P2P) mode of operation. For convenience and simplicity of explanation, A mobile device that has an NFC device and is capable of operating in an NFC mode of operation (eg, reader / writer mode and / or peer-to-peer mode) is referred to herein as an NFC-enabled mobile device 102. The operation of the NFC device on the mobile device 102 is controlled (at least to conduct transactions related to the present invention) by a mobile payment application installed on the NFC-enabled mobile device 102. For example, the operation of the mobile payment application is Device 102 activates (or activates) the NFC mode of operation of NFC-enabled mobile device 102, and mobile device 102 engages in the transaction. Allows data to be read from the NFC device 104. Data read from the NFC device 104 (or, in the embodiment described with respect to FIG. 3, data written to the NFC device 104) is paid or otherwise in accordance with the present invention. In connection with the purpose of the transaction, it is obtained and used by the mobile payment application.

  As described in the related application, the purchase or other transaction process associated with the embodiment generates, scans, or obtains a unique code (referred to herein as a “checkout token”) regarding the transaction time. Includes processing. With respect to the example shown in FIG. 1, the checkout token associated with the transaction time point is read by the NFC device of the NFC-compatible mobile device 102 from the NFC device 104 associated with the transaction time information management device 106. As described in the related application, in one embodiment, checkout tokens are dynamically generated for use in individual transactions at a particular merchant or location. As used herein, such dynamically generated checkout tokens are referred to as “dynamic tokens” or “dynamic checkout tokens”. A checkout token may be a token generated based on one or more information items, e.g. information related to a specific transaction point in time (e.g. terminal identifier and / or merchant identifier), related to transaction date and time. And / or tokens generated based on information relating to transaction amounts or other details relating to the transaction.

  The checkout token may be a static or fixed checkout token associated with the transaction time information management device 106. For example, a unique identifier may be specified for each transaction point.

  In one embodiment, the NFC-enabled mobile device 102 reads the checkout token (which can be a static token or a dynamic token) to complete the transaction. In addition, information is transmitted from the NFC-compatible mobile device 102 to the transaction management system 108. For one embodiment, the information regarding the checkout token includes identifying or selecting an appropriate payment amount for the transaction, associating the NFC-enabled mobile device 102 (and its owner) with the transaction, and a point-of-transaction information management device 106. May be used in obtaining information related to an ongoing transaction with.

  In the embodiment shown in FIG. 1, the NFC device 104 communicates with the transaction time information management device 106 via the communication interface 110, and the transaction time information management device 106 is (1) an NFC tag (or NFC tag) located in the NFC device 104 (or Update any device that emulates or simulates any of a wide variety of NFC tags) or (2) information from an NFC tag (or device that emulates an NFC tag) received from an NFC-enabled mobile device 102 Makes it possible to read For example, the communication interface 110 may be a wired interface (eg, a serial interface) or a wireless interface (eg, Bluetooth, ZigBee). For one embodiment, the NFC device 104 is encoded in an NFC Data Exchange Format (NDEF), such as, for example, NFC Forum Type 1-Type 4 tag for ISO / IEC 14443, Felica or ISO / IEC 14443, etc. NFC tag may be included.

  The data transmitted to the NFC device 104 may include data formatted for a data exchange format such as the NFC Forum Data Exchange Format (NDEF). For example, the transaction point of time information management device 106 is provided with a code that allows data to be transmitted to the NFC device 104 in a certain format, which format allows the NFC device 104 to operate on the data. Enabling data (such as static or dynamic checkout tokens) to be stored in the memory of the NFC device 104 and readable by an NFC device such as the NFC-enabled mobile device 102 To.

  In one embodiment, for example, an application is provided to the transaction point information management device 106, and the application is generated by the transaction point information management device 106 (or accessible to the transaction point information management device 106). Is encapsulated. The checkout token may be encapsulated in a single NDEF message or a group of NDEF messages (or NDEF message groups), and the checkout token data is provided to the NFC device 104 to write to the NFC tag of the NFC device 104 Allows to be done. For one embodiment, the point-of-transaction information management device 106 may generate an NDEF message each time a checkout token is generated or confirmed. That is, in one embodiment, each time a checkout token is generated or confirmed, the transaction point of time information management device 106 operates to cause the checkout token to be written or stored in the NFC tag of the NFC device 104. . The checkout token data is then notified to an NFC-enabled mobile device, such as device 102, for use in transactions related to the present invention. For example, when the NFC-enabled mobile device 102 receives a checkout token, the message analyzer (e.g., NDEF message analyzer) disassembles the message and passes the payload (including the checkout token) to a processing application. hand over. For one embodiment, the checkout token is provided to the mobile payment application for further processing (the further processing sends, for example, the checkout token and other data to the transaction management system 108, , Enabling mobile device 102 to be associated with a transaction including transaction point-of-time information management device 106).

  In one embodiment, for each transaction, a checkout token is generated (or identified or identified) and sent to the NFC device 104 (eg, by a message such as an NDEF message). For example, an NDEF message that encapsulates or encloses a checkout token is triggered or prompted by a cashier that initiates a transaction at a transaction point-of-time information management device. As another example, an NDEF message that encapsulates a checkout token is triggered or prompted by a customer who directs the point-of-transaction manager 106, who wants to conduct a transaction using a mobile device. ing.

  In one embodiment, a checkout token is generated (or identified or identified) and sent to the NFC device 104 less frequently (by a message such as an NDEF message). For example, in one embodiment, a static checkout token may be generated (or identified) to uniquely identify or identify a transaction at a particular point in time. Such a static checkout token need not be generated for each of the transactions; rather, the token may be generated or specified as needed to ensure a token that uniquely identifies the transaction point-in-time information. In such an embodiment, the point-of-transaction information management device 106 encapsulates static checkout token data and sends it to the NFC device 104 (via a message such as an NDEF message) as needed.

  Data included in an NDEF (or other) message includes a message type identifier (eg, may be an NDEF-specified type, or a custom message type). In addition, the message may include other information useful to the NFC device when reading and processing data.

  In one embodiment, the NFC tag of the NFC device 104 is written such that it can be read by the NFC-enabled mobile device 102 operating in read / writer mode or peer-to-peer mode. A transaction example including the example of FIG. 1 will be described with reference to FIG.

  The process of FIG. 2 is generally illustrated in terms of merchants or other transaction processing points. For example, the transaction process 200 may be performed by or at a merchant having a point-of-transaction information management device 106 having an NFC device 104. The process begins at 202 and the goods or services are recorded at the cash register to calculate the total purchase. The process continues to 204 where the point-of-transaction information management device 106 (or clerk) prompts the customer to select a payment option (option) and determines whether a mobile payment option is selected. If no mobile payment option is selected, the process continues at 206 with processing to complete a purchase utilizing other payment options or standard payment processing.

  If the mobile payment option is selected, the process continues at 208 and the point-of-transaction manager 106 (or the associated merchant system) generates or obtains a checkout token. For example, the transaction point-of-time information management device 106 operates to generate or specify a static or dynamic checkout token to use for the transaction. In a non-limiting embodiment, the point-of-transaction information management device 106 includes a merchant checkout token, transaction amount, and other transaction data (e.g., terminal identifier, date, time, additional transaction data, etc.). A merchant payment authentication request (request message) is generated and transmitted to the transaction management system 108. The merchant payment authorization request is used by the transaction management system 108 (eg, as mentioned in the related application above) to create a transaction for processing in the merchant transaction queue. In one embodiment, the checkout token is not transmitted from the point-of-transaction information management device 106, as mentioned in the related application. In that case, the checkout token is extracted, generated or “looked up or referenced” by the transaction management system 108 in response to the message received at the transaction point information management device 106-208. For example, the checkout token may be referenced and extracted from a table that associates the merchant ID (received at 208) with a static checkout token. In one embodiment, a checkout token is generated by the transaction management system 108 when the transaction management system 108 receives a merchant payment authorization request at 208, after which the checkout token is an acknowledgment of the merchant payment authorization request. It may be returned to the transaction time information management device 106 as a part. Although the process at 208 is illustrated as including a checkout token sent from the merchant to the transaction management system 108, in one embodiment, the token is not sent at 208, but instead a checkout token is traded. It may be provided by the management system 108.

  The process continues at 210 where the checkout token may be made available to the customer by the NFC device 104 so that the customer can obtain the checkout token using the NFC reader of the mobile device 102. The process 210 includes operating the transaction point of time information management device 106 to encapsulate or include a checkout token in a message (e.g., NDEF message or group of messages) for provision to the NFC device 104 (e.g., Causes the NFC device to be updated with data associated with the checkout token). The customer can then, for example, within the range of the NFC reader, by a store clerk (or with an instruction token) to tap or present his NFC-enabled mobile device 102 to the touch point or area of the NFC device 104. ) Guided. Upon successful reading of data from the NFC device, the mobile payment application installed on the mobile device 102 may provide a confirmation signal or a message to confirm.

  When the checkout token is properly read by the mobile device 102, a message containing the checkout token is used to match payment details with customer payment information, as described in the related application. Sent from the mobile device 102 to the transaction management system 108. The point of sale information management process continues at 212 and the point of sale information management device 106 (eg, indirectly or directly by an intermediary system such as a payment gateway, store point of sale information management system, etc.) from the transaction management system 108. Receive merchant payment authorization response message. The payment amount selected by the customer (using his mobile device 102) is verified for the purchase transaction after the prescribed customer-related processing and transaction management system-related processing (also described in the related application) is complete. After that, a merchant payment authentication response message is generated by the transaction management system 108. The process continues at 214 and the transaction point of time information management device 106 operates to generate a transaction receipt (receipt) to complete the transaction. These series of messages are shown for illustrative purposes only. In one embodiment, transaction processing may be performed in a different order, for example, checkout to initiate processing prior to any communication between the transaction point-of-time information management device 106 and the transaction management system 108. The token is read by the NFC compatible mobile device 102.

  As mentioned in the related application, in one embodiment, the process of FIG. 2 may be modified so that the merchant sends a merchant payment authorization request before the transaction total is calculated. Further, in such an embodiment, the customer may operate their NFC-enabled mobile device 102 to read the checkout token before the transaction total is calculated.

For one embodiment, the NFC-enabled mobile device 102 may be configured to write data to the NFC device 104 and distribute a checkout token or code to the transaction time information management device 106. In such an embodiment, the NFC-enabled mobile device 102
It is configured to operate in a write mode, allowing the NFC-enabled mobile device 102 to pass a checkout token or code to the transaction time information management device 106. One existing payment method uses the NFC function of the mobile device to deliver encrypted cardholder data to the payment terminal. Such schemes as described in the background art require effective and complex encryption and credit guarantee schemes to make payments. Embodiments of the present invention avoid expensive and complex schemes when operating in the mode as shown in FIG. 3, and the reason for doing so is transmitted from the mobile device 102 to the transaction point of time information management device 106. This is because the only information that is available is a static or dynamic checkout token that is used to associate the NFC-enabled mobile device 102 with the point-of-transaction information management device 106, thereby making ongoing progress on those devices. A transaction is uniquely identified. In one embodiment, the checkout token is obtained by the NFC-enabled mobile device 102 from the transaction management system 108 prior to (or during) execution of the transaction. In one embodiment, the checkout token is obtained by the NFC enabled mobile device 102 prior to the transaction and stored or cached for use. This is even in situations where the NFC-enabled mobile device 102 cannot reach the transaction management system 108 during a transaction (e.g., even where the transaction location is limited to a wireless or cellular connection). The transaction according to the present invention is made feasible.

  As shown in FIG. 3, a transaction in such an embodiment may be processed as follows. The process begins at 302, where goods or services are recorded at the cash register to sum the purchase amount. The process continues at 304 where the point-of-transaction manager 106 (or store clerk) prompts the customer to select a payment option and determines whether a mobile payment option is selected. If the mobile payment option is not selected, the process continues at 306 with other payment options being used to complete the purchase or normal payment processing.

  The process continues at 308, where the customer selects an option related to the mobile payment application of the NFC-enabled mobile device 102, generates (or obtains) a checkout token, and checks out to the NFC device 104 associated with the transaction time information management device 106. Write the token. This checkout token is written from the NFC device of the NFC-compatible mobile device 102 to the NFC device 104 by wireless communication (for example, via the contactless communication interface 112 in FIG. 1). When the checkout token is received by the NFC device 104, the checkout token is notified (via the interface 110 of FIG. 1) to the transaction point-of-time information management device 106 that generates one or more messages to the transaction management system 108. The For example, when the transaction time information management device 106 receives a checkout token, it generates a merchant payment request message including details of the transaction (for example, including transaction amount, merchant information, transaction time information management device information, etc.) May be. The details (items) of the transaction are transmitted to the transaction management system 108 together with the checkout token. The process of trading continues as described with respect to FIG. 2 (also mentioned in the related application). In this way, the present embodiment allows the NFC-enabled mobile device 102 to conduct transactions in the NFC write mode, regardless of encryption methods that are complex, expensive, and insecure.

  Whether the NFC-enabled mobile device 102 operates in writer mode (FIG. 3) or reader mode (FIG. 2), the embodiments provide many advantages. For example, embodiments enable card associations, TSMs, by enabling NFC-based payment schemes for mobile devices and terminals and bypassing the constraints that must use the secure element functionality of the NFC controller chip. Bypass the fees and restrictions of carrier and handset manufacturers. Further, embodiments may allow NFC-enabled mobile devices using reader / writer mode to provide secure mobile payment and mobile offer redemption functionality without utilizing card emulation NFC and secure elements. . Embodiments can complete contactless payment transactions without using card emulation mode NFC even in situations where a wireless connection is not available to the mobile device.

  The above description of the process according to the present application should not be construed to perform the process steps in a fixed order. Instead, the process steps may be performed in any order that is feasible, including when at least some steps are performed simultaneously.

  Those skilled in the art who understand the present disclosure will appreciate that a wide variety of hardware and software forms may be used to implement the features of the present invention. As one specific example (but not limited), the point-of-transaction information management device is an RC-S801NFC dynamic tag provided by Sony (which may be referred to as `` FeliCa Plug ''). It may be connected. In one embodiment, the RC-S801NFC dynamic tag may be connected via a wired interface to receive a checkout token from an external system (such as, for example, a point-of-sale (POS) device). . Once received, the RC-S801NFC dynamic tag creates checkout token data presented with the RC-S801 NFC tag, which is read by the NFC-enabled mobile device 102 operating in NFC reader mode. Made available as is. The reverse process can also be used. That is, the RC-S801NFC dynamic tag can operate so as to receive a value (for example, a checkout token) provided by the NFC-compatible mobile device 102 operating in the reader / writer mode. Many other commercially available tags may be used to construct the system of the present invention.

  In one embodiment, the checkout token may be read (or written) utilizing an NFC controller present in many NFC-enabled mobile devices. For example, many devices include an NFC controller such as NXP-PN532 that can read and write NRF tags. Such an NFC controller emulates a standard NFC tag and allows it to function as a transaction point of time information management device 106. That is, the NFC-compatible mobile device 102 formed by such a method is controlled to present a checkout token to the NFC-compatible mobile device 102 by the NFC reader / writer mode function, or from the NFC-compatible mobile device 102 It can be controlled to receive a checkout token.

  In many NFC phones with an NFC controller, such as NXP-PN532 (available from NXP Semiconductors), which can read and write NFC tags, use the means according to this application along with such an NFC controller. It is a thing. They can also emulate standard NFC tags, which can be used to present a checkout token to an NFC-enabled mobile device, or an NFC-enabled mobile device with an NFC reader / writer mode function. It means that it can function as a transaction point-of-time information management device that can be received from. By enabling a checkout token to be transmitted between such devices, a transaction according to the present invention may be performed.

  While the invention has been described in connection with specific embodiments, various modifications, obvious to those skilled in the art, may be made without departing from the spirit and scope of the invention as described in the appended claims. It should be understood that substitutions and substitutions may be made to the disclosed embodiments.

Claims (24)

A transaction time information management device for identifying information related to a transaction, the transaction time information management device identifying a checkout token used for the transaction;
An NFC device that receives the checkout token from the transaction time information management device by communication with the transaction time information management device, wherein the checkout token is used in a mobile application of an NFC-compatible mobile device, An NFC device that wirelessly notifies an NFC reader of the NFC-compatible mobile device.   The system according to claim 1, wherein the transaction time information management device confirms a request from a customer to perform the transaction using an NFC-compatible mobile device.   The system of claim 1, wherein the NFC reader of the NFC-enabled mobile device operates in a reader / writer mode.   The system according to claim 1, wherein the NFC device communicates with the transaction time information management device through a wired interface.   The system according to claim 1, wherein the checkout token is updated in the NFC device under the control of the transaction time information management device.   The system of claim 1, wherein the checkout token is received at the transaction time information management device from a remote transaction management system before sending a transaction code to the NFC device.   The system according to claim 1, wherein the transaction time information management device and the NFC device are formed as a single device.   The system of claim 1, wherein the checkout token is received at the NFC device from a remote transaction management system.   The system according to claim 1, wherein the checkout token is a static code specified by a transaction management system used in a transaction in the transaction time information management device.   The system according to claim 1, wherein the checkout token is generated by the transaction time information management device before transmitting the checkout token to the NFC device.   The system according to claim 1, wherein the checkout token is generated by a store sales point information management system and provided to the transaction point information management device for transmission to the NFC device.   The system according to claim 1, wherein the process of receiving the checkout token from the transaction time information management device includes including the checkout token in a message wrapper and transmitting the message wrapper to the NFC device.   The system according to claim 1, wherein the transaction time information management device is another NFC-compatible mobile device. A transaction time information management device that identifies information related to a transaction related to a transaction time information management device and a customer, and a transaction time information management device that confirms a request from the customer to make a payment using an NFC-compatible mobile device;
An NFC device that communicates with the transaction time information management device and operates in a reader / writer mode to write a checkout token to the NFC device when the NFC-compatible mobile device is located in the vicinity of the NFC device An NFC device that wirelessly receives the checkout token from the NFC-enabled mobile device and transmits the received checkout token to the transaction time information management device to complete the transaction.   15. The system of claim 14, wherein the checkout token is generated by a transaction management system used by the NFC enabled mobile device when performing a transaction.   The system of claim 14, wherein the checkout token is selected from a plurality of checkout tokens accessible by the NFC-enabled mobile device.   15. The system according to claim 14, wherein the transaction time information management device is another NFC-compatible mobile device. A method for conducting a payment transaction,
A step of summing the purchase amount in the store point-of-sale information management device;
Confirming that the mobile payment option has been selected;
Updating the NFC device in the point-of-sales information management device with a checkout token, wherein the checkout token is wirelessly transmitted from the NFC device to the mobile device by a customer via an NFC interface; and ,
Receiving a payment authorization from a transaction management system.   The method of claim 18, wherein the payment authorization is received from the transaction management system after both the mobile device and the point-of-sale information management device separately transmitted a checkout token to the transaction management system.   The method according to claim 18, wherein the NFC device communicates with the point-of-sale information management device through a wired serial interface. A method for conducting a payment transaction,
A step of summing the purchase amount in the point-of-sale information management device;
Confirming that the mobile payment option has been selected;
Receiving a checkout token from a mobile device operated by a customer, wherein the checkout token is between the NFC device of the mobile device and another NFC device in communication with the point-of-sale information management device Received by wireless communication; and
Sending a merchant payment request including the checkout token and purchase transaction data to a transaction management system;
Receiving a payment authorization from a transaction management system.   The method of claim 21, wherein the checkout token is identified by a mobile payment application running on the mobile device.   The method of claim 21, wherein the checkout token is stored prior to a payment transaction by a mobile payment application.   The method of claim 21, wherein the checkout token is identified by a mobile payment application during the payment transaction.

Images