EP2850572A1 - Systèmes et procédés de traitement de transaction de communication en champ proche (nfc) - Google Patents

Systèmes et procédés de traitement de transaction de communication en champ proche (nfc)

Info

Publication number
EP2850572A1
EP2850572A1 EP13791465.1A EP13791465A EP2850572A1 EP 2850572 A1 EP2850572 A1 EP 2850572A1 EP 13791465 A EP13791465 A EP 13791465A EP 2850572 A1 EP2850572 A1 EP 2850572A1
Authority
EP
European Patent Office
Prior art keywords
transaction
nfc
point
checkout token
payment
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP13791465.1A
Other languages
German (de)
English (en)
Other versions
EP2850572A4 (fr
Inventor
Kevin Laracey
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
PayPal Inc
Original Assignee
Paydiant LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US13/731,348 external-priority patent/US9400978B2/en
Priority claimed from US13/768,156 external-priority patent/US9305295B2/en
Application filed by Paydiant LLC filed Critical Paydiant LLC
Publication of EP2850572A1 publication Critical patent/EP2850572A1/fr
Publication of EP2850572A4 publication Critical patent/EP2850572A4/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/327—Short range or proximity payments by means of M-devices
    • G06Q20/3278—RFID or NFC payments by means of M-devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/108—Remote banking, e.g. home banking
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/20—Point-of-sale [POS] network systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/327—Short range or proximity payments by means of M-devices
    • G06Q20/3276—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being read by the M-device
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0241—Advertisements
    • G06Q30/0251—Targeted advertisements
    • G06Q30/0253—During e-commerce, i.e. online transactions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions

Definitions

  • NFC near field communication
  • the NFC device In reader/writer mode, the NFC device is capable of reading NFC Forum- mandated tag types, such as in the scenario of reading an NFC Smart Poster tag.
  • the reader/writer mode on the RF interface is compliant with the ISO/IEC 14443 and FeliCa schemes.
  • peer-to-peer mode two NFC devices can exchange data (e.g., two devices can share Bluetooth or WiFi link set up parameters, or exchange virtual business cards or digital photos). Peer-to-peer mode is based on the ISO/IEC 18092 standard.
  • card emulation mode an NFC device appears to an external reader much the same as a traditional contactless smart card. Card emulation mode enables contactless payments and ticketing by NFC devices without changes to the existing payment processing infrastructure.
  • a number of smart phones include NFC technology.
  • Globoplatform/JCOP which is essentially a Java runtime environment implemented on an NFC chip
  • each payment card stored on the chip have its own Java application that manages the encryption and decryption of that card's data using a unique set of keys.
  • the complexity and security considerations associated with managing different proprietary key schemes have resulted in the creation of a new entity in the NFC payments ecosystem called a Trusted Service Manager.
  • the TSM has the job of serving as a trusted intermediary charged with managing the movement of encrypted payment card credentials using multiple encryption schemes to consumers' handsets.
  • the TSM exists since the different associations have different schemes, and the associations do not want to share their specific encryption and card management schemes with one another, among other considerations. It is estimated that use of a TSM can add as much as $5 per year in cost to having a payment card stored and managed on a consumers' smartphone using card emulation mode NFC.
  • card emulation mode NFC to facilitate payments has also created the opportunity for handset makers, and wireless carriers to attempt to control the process of placing payment cards on devices equipped with NFC card emulation mode capable chips.
  • Wireless carriers such as Verizon and ATT working together as part of the Isis Consortium, and handset makers such as Google are attempting to charge significant fees to payment card issuers either in the form of licensing fees or co-marketing dollars, something that is not appealing to banks, who are the primary issuers of payment cards. Industry experts believe that Isis is proposing that banks pay nearly $10 per payment card per year to make a payment card available in an NFC enabled mobile phone from ATT or Verizon.
  • FIG. 1 is a block diagram depicting a system configured pursuant to some embodiments.
  • FIG. 2 is a flow diagram depicting a process pursuant to some embodiments.
  • FIG. 3 is a flow diagram depicting a further process pursuant to some
  • Embodiments of the present invention relate to systems, methods, processes, computer program code, and means for employing the near field communication ("NFC") functionality of mobile devices for use in payment transactions.
  • NFC near field communication
  • embodiments may be deployed in conjunction with a system such as that described by the inventors in their co-pending and commonly assigned applications referenced above in which mobile devices may be used to conduct transactions by scanning, capturing, or otherwise entering a code associated with a transaction.
  • NFC near field communication
  • embodiments may be used in conjunction with payment or other transaction systems in which a mobile device is used to initiate a transaction by generating or otherwise obtaining a checkout token or other code and providing the checkout token or code to a second device involved in the transaction (such as a merchant point of sale device, an automated teller machine, a kiosk, a device of another individual, or the like) using NFC technologies.
  • a mobile device is used to initiate a transaction by generating or otherwise obtaining a checkout token or other code and providing the checkout token or code to a second device involved in the transaction (such as a merchant point of sale device, an automated teller machine, a kiosk, a device of another individual, or the like) using NFC technologies.
  • embodiments of the present invention are not limited to use in conjunction with the payment or transaction systems described in our co-pending applications. Instead, the use of NFC functionality as described herein may be used with desirable results and benefits in a wide variety of payment or transaction systems, digital wallets, or the like. Further, while embodiments are described herein generally in reference to transactions (such as payment transactions), embodiments may be used with desirable results in other types of transactions such as loyalty, reward or other offer type of transactions where one device (such as a mobile) may interact with another device (such as another mobile device or a point of transaction).
  • FIG. 1 is a block diagram of a system 100 pursuant to some embodiments. Further details of the system 100 may be obtained by reference to our copending applications incorporated by reference herein.
  • a payment account holder, buyer, or other user or operator may have or use a mobile device 102 (such as a mobile telephone or the like).
  • the mobile device 102 has a display screen and a data entry device (such as a keypad or touch screen).
  • the customer may use the mobile device 102 to conduct a transaction with a merchant or other entity (such as a bank) via a point of transaction device 106.
  • the point of transaction device 106 may be, for example, a point of sale terminal, an automated teller machine, another mobile device (e.g., such as a portable point of sale terminal, another individual's mobile device, etc.), or the like.
  • the merchant may be a physical storefront, electronic commerce merchant, or mail order and telephone ("MOTO") merchant, or another person or entity. Further, the merchant need not be a "merchant", but may also be another individual (in the case of person to person transactions), or a kiosk or other unattended device (such as an automated teller machine ("ATM”) or the like.
  • ATM automated teller machine
  • the device associated with a customer, consumer, or other entity acting as a purchaser in a transaction will be referred to herein as the “mobile device 102" or “NFC enabled mobile device 102".
  • the device associated with a merchant, vendor, funds recipient, or other entity acting as a seller or funds recipient in a transaction will be referred to as the "point of transaction device 106".
  • the point of transaction device 106 may be a traditional merchant point of sale device adapted to operate pursuant to the present invention, or it may be a device such as a mobile telephone or other device (e.g., in some embodiments, a customer may operate a mobile device and the merchant or other participant in a transaction may also operate a mobile device).
  • the mobile device 102 is an NFC-enabled mobile device such as a mobile telephone having a radio frequency identification (“RFID”) chip installed therein (either as a part of the mobile telephone's chip set, or installed as an after-market SIM card).
  • RFID radio frequency identification
  • the mobile telephone may be a Google® Nexus S, or a Blackberry® 9600 smartphone each of which have RFID chips installed therein.
  • the mobile device 102 may be operated pursuant to one or more standards, such as, for example, the ISO/IEC 18092, NFC IP-1 and ISO/IEC 14443 contactless communication standards or the like.
  • the mobile device 102 may be operated in the so-called "reader/writer” mode in which the NFC device in the mobile device 102 is capable of reading data from NFC Forum compatible NFC tags (such as an NFC tag in the NFC device 104).
  • the mobile device 102 may further (or alternatively) be capable of operating in the so-called “peer-to-peer” mode of operation.
  • a mobile device which has an NFC device and that is capable of operating in an NFC mode of operation (such as in reader/writer mode and/or peer-to-peer mode, for example) will be referred to herein as an NFC enabled mobile device 102.
  • the operation of the NFC device in the NFC enabled mobile device 102 may be controlled (at least for the purposes of transactions conducted pursuant to the present invention) via a mobile payment application installed on the NFC enabled mobile device 102.
  • operation of the mobile payment application may cause the NFC enabled mobile device 102 to activate or enable an NFC mode of operation of the NFC enabled mobile device, allowing the mobile device 102 to read data from an NFC device 104 associated with a point of transaction.
  • the data read from the NFC device 104 (or, in an embodiment discussed further below in conjunction with FIG. 3, the data written to the NFC device 104) is captured by the mobile payment application and used in conjunction with payment or other transactions pursuant to the present invention.
  • a purchase or other transaction process pursuant to some embodiments include the generation, scanning or capturing of a unique code (referred to herein as a "checkout token") associated with the point of transaction.
  • a checkout token a unique code associated with the point of transaction.
  • the checkout token associated with the point of transaction is read by an NFC device in the NFC enabled mobile device 102 from an NFC device 104 associated with the point of transaction 106.
  • the checkout token may be dynamically generated for use in individual transactions at specific merchants or locations. As used herein, such a dynamically generated checkout token is referred to as a "dynamic token” or “dynamic checkout token”.
  • a dynamic checkout token may be a token that is generated based on one or more items of information such as, for example, information associated with the specific point of transaction (such as a terminal identifier and/or a merchant identifier), information associated with a date and time of the transaction, and/or information associated with the transaction amount or other transaction details.
  • the checkout token may also be a static checkout token associated with a specific point of transaction 106.
  • a specific identifier may be assigned to an individual point of transaction.
  • the reading of the checkout token (whether it be a static token or a dynamic token) by the NFC enabled mobile device 102 causes information to be transmitted from the NFC enabled mobile device 102 to a transaction management system 108 for use in completing a transaction.
  • data associated with the checkout token may be used in conjunction with identifying or selecting an appropriate payment account for the transaction, for associating the NFC enabled mobile device 102 (and its holder) with a transaction, or for otherwise obtaining information about a pending transaction with a point of transaction 106. In the embodiment depicted in FIG.
  • the NFC device 104 is in communication with the point of transaction device 106 via a communication interface 110 which allows the point of transaction device 106 to operate to either (1) update an NFC tag (or a device that emulates one of the many varieties of NFC tags) located in the NFC device 104, or (2) read information from an NFC tag (or a device that emulates an NFC tag) received from an NFC enabled mobile phone 102.
  • the communication interface 1 10 may be a wired interface (such as, for example, a serial interface or the like) or a wireless interface (such as a Bluetooth, ZigBee, or the like).
  • the NFC device 104 may include an NFC tag encoded in the NFC Data Exchange Format ("NDEF") such as, for example, an NFC Forum Type 1 - Type 4 tag pursuant to ISO/IEC 14443 A, FeliCa, or ISO/IEC 14443.
  • NDEF NFC Data Exchange Format
  • the data transmitted to the NFC device 104 may include data that is formatted pursuant to a data exchange format such as the NFC Forum Data Exchange Format ("NDEF").
  • NDEF NFC Forum Data Exchange Format
  • the point of transaction device 106 may be provided with code allowing data (such as a static or dynamic checkout token) to be transmitted to the NFC device 104 in a format that allows the NFC device 104 to operate on the data such that the data (such as a static or dynamic checkout token) is stored in a memory of the NFC device 104 and accessible to be read by an NFC device such as an NFC enabled mobile device 102.
  • the point of transaction device 106 may be provided with an application that encapsulates checkout tokens generated by (or otherwise accessible to) the point of transaction device 106.
  • the checkout tokens may be encapsulated into a single NDEF message or a group of NDEF messages that allow the checkout token data to be provided to the NFC device 104 for writing into an NFC tag of the NFC device 104.
  • the point of transaction 106 may generate an NDEF message each time a checkout token is generated or identified. That is, in some embodiments, each time a checkout token is generated or identified, the point of transaction 106 is operated to cause the checkout token to be written to or stored in an NFC tag of the NFC device 104.
  • the checkout token data may then be communicated to an NFC enabled mobile device such as device 102 for use in a transaction pursuant to the present invention.
  • a message parser such as an NDEF message parser
  • the checkout token is passed to a mobile payment application for further processing (which may include, for example, transmitting the checkout token and other data to a transaction management system 108 to allow the transaction management system 108 to associate the mobile device 102 with a transaction involving the point of transaction 106).
  • the checkout token may be generated (or otherwise identified) and transmitted (in a message such as an NDEF message) to NFC device 104 on a per-transaction basis.
  • the NDEF message encapsulating a checkout token may be triggered or prompted by a cashier initiating a transaction at the point of transaction.
  • the NDEF message encapsulating the checkout token may be triggered or prompted by a customer (or holder of an NFC enabled mobile device 102) instructing a point of transaction 106 that the customer wishes to conduct a transaction using a mobile device.
  • the checkout token may be generated (or otherwise identified) and transmitted (in a message such as an NDEF message) to NFC device 104 on a less frequent basis.
  • a static checkout token may be generated (or otherwise identified) to uniquely identify a particular point of transaction.
  • Such a static checkout token need not be generated for each transaction; instead, the token may be generated or identified as needed to ensure the token uniquely identifies the point of transaction.
  • the point of transaction 106 may encapsulate the static checkout token data and transmit it (in a message such as an NDEF message) to NFC device 104 as needed.
  • the data encapsulated in the NDEF (or other) message may include a message type identifier (which may be, for example, an NDEF-specified type, or a custom message type). Further, the message may include other information useful to an NFC device for reading and acting on the data.
  • the NFC tag in the NFC device 104 is written such that it is available to be read by an NFC enabled mobile device 102 operating in read/writer mode or in peer-to-peer mode.
  • An example transaction involving the embodiment of FIG. 1 will now be described by reference to FIG. 2.
  • transaction process 200 may be performed by or at a merchant location that has a point of transaction device 106 having an NFC device 104. Processing begins at 202 where the goods or services are rung up to total the purchase. Processing continues at 204 where the point of transaction device 106 (or the clerk) prompts the customer to select a payment option, and a determination is made whether a mobile payment option is selected. If the mobile payment option is not selected, processing continues at 206 where standard payment processing or processing to complete the purchase using another payment option occurs.
  • the point of transaction device 106 (or other associated merchant systems) generates or otherwise obtains a checkout token.
  • the point of transaction device 106 may be operated to generate or assign a static or a dynamic checkout token for use in conjunction with the transaction.
  • the point of transaction device 106 may create and transmit a merchant payment authorization request, including a merchant checkout token, a transaction amount, and other transaction data (such as a terminal identifier, date, time, enhanced transaction data, etc.) to a transaction management system 108.
  • the merchant payment authorization request is then used by the transaction management system 108 (as described, for example, in our co-pending applications), to create a pending transaction in a merchant transaction queue.
  • the checkout token is not sent from the point of transaction device 106. Instead, the checkout token may be retrieved, generated or "looked up" by the transaction management system 108 in response to a message received at 208 from the point of transaction 106. For example, the checkout token may be looked up from a table associating a merchant ID (received at 208) with a static checkout token.
  • the checkout token could be generated by the transaction management system 108 when it receives the merchant payment authorization request at 208, and then the checkout token would be passed back to the point of transaction 106 as part of the acknowledgement of the merchant payment authorization request.
  • processing at 208 is shown as including a checkout token transmitted from the merchant to the transaction management system 108, in some embodiments, the token is not sent at 208, instead, the checkout token is provided by the transaction management system 108.
  • a checkout token may be made available to the customer via the NFC device 104 so that the customer may capture the checkout token using an NFC reader in the mobile device 102.
  • Processing at 210 may include the operation of the point of transaction device 106 to encapsulate the checkout token into a message (such as an NDEF message or messages) for provision to the NFC device 104 (e.g., to cause the NFC device to be updated with data associated with the checkout token).
  • the customer may then, for example, be instructed by a clerk (or by signage associated with the NFC device 104) to tap or present their NFC enabled mobile device 102 to a touch point or area on the NFC device 104 within range of the NFC reader.
  • a mobile payment application installed on the mobile device 102 may provide a
  • a message containing the checkout token is transmitted from the mobile device 102 to the transaction management system 108 for use in matching the payment details with the customer's payment information as described in our co-pending applications.
  • Processing at the point of transaction continues at 212 where the point of transaction device 106 receives a merchant payment authorization response message from the transaction management system 108 (either directly or indirectly via intermediate systems such as a payment gateway, a point of sale system, or the like).
  • authorization response message is generated by the transaction management system 108 after certain customer-related processing steps and transaction management system- related processing steps (described in our co-pending applications) have been completed, and after a payment account selected by the customer (using their mobile device 102) has been authorized for the purchase transaction. Processing continues at 214 where the point of transaction device 106 is operated to cause the generation of a transaction receipt to complete the transaction.
  • the sequence of these messages is provided for illustrative purposes only. In some embodiments, the transaction processing may be performed in a different order - for example, a checkout token may be read by an NFC enabled mobile device 102 to initiate processing prior to any communication between the point of transaction 106 and the transaction management system 108.
  • the process of FIG. 2 may be modified to allow the merchant to transmit a merchant payment authorization request before the transaction total has been calculated. Further, in such embodiments, the customer may operate their NFC enabled mobile device 102 to read the checkout token before the transaction total has been calculated.
  • the NFC enabled mobile device 102 may be configured to write data to the NFC device 104 to deliver a checkout token or code to the point of transaction device 106.
  • the NFC enabled mobile device 102 is configured to operate in an NFC writer mode, enabling the NFC enabled mobile device 102 to pass a checkout token or code to the point of transaction device 106.
  • Certain existing payment schemes use the NFC capabilities of a mobile device to pass encrypted cardholder data to the payment terminal. Such schemes, as described in the background section above, require expensive and complex encryption and credentialing schemes to facilitate payments.
  • Embodiments of the present invention when operating in a mode as shown in FIG. 3, avoid such expense and complication, as the only information that is transmitted from the mobile device 102 to the point of transaction 106 is a static or dynamic checkout token used to associate the NFC enabled mobile device 102 to the point of transaction 106 such that a pending transaction involving the devices may be uniquely identified.
  • the checkout token is obtained by the NFC enabled mobile device 102 from the transaction management system 108 prior to (or during) the conduct of the transaction.
  • the checkout token may be obtained by the NFC enabled mobile device 102 prior to a transaction and cached for use. This allows a transaction pursuant to the present invention to be performed even in situations where the NFC enabled mobile device 102 is unable to reach the transaction management system 108 during a transaction (e.g., in situations where a transaction location has limited wireless or cellular connectivity available).
  • a transaction in such an embodiment may proceed as follows. Processing begins at 302 where the goods or services are rung up to total the purchase. Processing continues at 304 where the point of transaction device 106 (or the clerk) prompts the customer to select a payment option, and a determination is made whether a mobile payment option is selected. If the mobile payment option is not selected, processing continues at 306 where standard payment processing or processing to complete the purchase using another payment option occurs. Processing continues at 308 where the consumer selects an option on a mobile payment application on the NFC enabled mobile device 102 to generate (or otherwise obtain) a checkout token and to write the checkout token to the NFC device 104 associated with the point of transaction device 106.
  • This checkout token is written from an NFC device on the NFC enabled mobile device 102 to the NFC device 104 via wireless communication (such as over a contactless communication interface 112 of FIG. 1).
  • the checkout token is received by the NFC device 104, it is communicated (via interface 1 10 of FIG. 1) to the point of transaction device 106 for use in generating one or more messages to the transaction management system 108.
  • the point of transaction device 106 may, upon receipt of the checkout token, generate a merchant payment request message that includes transaction details (including, for example, a transaction amount, merchant information, point of transaction information, or the like).
  • the transaction details, along with the checkout token are transmitted to the transaction management system 108. Processing of the transaction continues in a similar fashion as described above in conjunction with FIG. 2 (and as described in our co-pending applications). In this manner, embodiments allow NFC enabled mobile devices 102 to conduct transactions in NFC writer mode, without need for complex, expensive and potentially insecure encryption schemes.
  • embodiments provide a number of advantages. For example, embodiments enable NFC based payment schemes for mobile devices and terminals that bypass card association, TSM, carrier and handset maker fees and rules by bypassing the need to use the secure element capabilities of the NFC controller chip. Further, embodiments allow all NFC enabled mobile devices that support reader/writer mode to have secure mobile payment and mobile offer redemption functionality without using card emulation NFC and a secure element. Embodiments also enable the completion of a contactless payment transaction in situations where there is no wireless connection available to the mobile device, without using card emulation mode NFC.
  • a point of transaction may be connected to a RC-S801 NFC Dynamic Tag (also referred to as a FeliCa Plug) offered by Sony.
  • the RC-S801 NFC Dynamic Tag may be connected via a wired interface to receive a checkout token from an external system (such as a point of sale device or the like).
  • the RC-S801 NFC Dynamic Tag may make the checkout token data present on an NFC tag in the RC-S801 and the checkout token data may be made available to be read by an NFC enabled mobile device 102 operating in NFC reader mode.
  • the reverse process is also supported. That is, the RC-S801 NFC Dynamic Tag can be operated to receive a value (such as a checkout token) provided by an NFC enabled mobile device 102 operating in reader/writer mode.
  • a value such as a checkout token
  • a number of other commercially available tags may be configured for use in conjunction with the system of the present invention.
  • checkout tokens may be read (or written) using the NFC controller present in many NFC enabled mobile devices.
  • NFC controllers such as the NXP PN532 which can read and write NFC tags.
  • NFC controllers can also emulate standard NFC tags allowing them to serve as a point of transaction device 106. That is, an NFC enabled mobile device 102 configured in such a manner can be operated to present a checkout token to NFC enabled mobile device 102 or to receive a checkout token from an NFC enabled mobile device 102 with NFC reader/writer mode capabilities.
  • NFC controllers such as the NXP PN532 (available from NXP Semiconductors) which can read and write NFC tags. They can also emulate standard NFC tags, meaning that they can serve as a point of transaction device that can present a checkout token to an NFC enabled mobile device or receive a checkout token from an NFC enabled mobile device with NFC reader/writer mode capabilities. By allowing checkout tokens to be transmitted between such devices, transactions pursuant to the present invention may be performed.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Finance (AREA)
  • Cash Registers Or Receiving Machines (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

Conformément à des modes de réalisation, la présente invention concerne des systèmes, des procédés, des processus, un code de programme d'ordinateur et un moyen pour utiliser la fonctionnalité de communication en champ proche (« NFC ») de dispositifs mobiles destinés à être utilisés dans des transactions de paiement.
EP13791465.1A 2012-05-14 2013-05-14 Systèmes et procédés de traitement de transaction de communication en champ proche (nfc) Withdrawn EP2850572A4 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201261646523P 2012-05-14 2012-05-14
US13/731,348 US9400978B2 (en) 2010-04-09 2012-12-31 Methods and systems for selecting accounts and offers in payment transactions
US13/768,156 US9305295B2 (en) 2010-04-09 2013-02-15 Payment processing methods and systems
PCT/US2013/040953 WO2013173339A1 (fr) 2012-05-14 2013-05-14 Systèmes et procédés de traitement de transaction de communication en champ proche (nfc)

Publications (2)

Publication Number Publication Date
EP2850572A1 true EP2850572A1 (fr) 2015-03-25
EP2850572A4 EP2850572A4 (fr) 2016-01-06

Family

ID=49584211

Family Applications (1)

Application Number Title Priority Date Filing Date
EP13791465.1A Withdrawn EP2850572A4 (fr) 2012-05-14 2013-05-14 Systèmes et procédés de traitement de transaction de communication en champ proche (nfc)

Country Status (5)

Country Link
EP (1) EP2850572A4 (fr)
JP (1) JP2015525383A (fr)
CN (1) CN104641388B (fr)
BR (1) BR112014028407A2 (fr)
WO (1) WO2013173339A1 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10275827B2 (en) 2013-03-14 2019-04-30 Fexco Systems and methods for transferring funds using a wireless device
CN107818464A (zh) * 2016-09-14 2018-03-20 百度在线网络技术（北京）有限公司 一种在移动终端实现的nfc支付方法与装置
WO2021033477A1 (fr) * 2019-08-16 2021-02-25 フェリカネットワークス株式会社 Dispositif de traitement d'informations, système de traitement de règlements, procédé et programme
US20230222476A1 (en) 2022-01-11 2023-07-13 Pi-Xcels Co., Ltd. Method of issuing electronic receipts

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001344545A (ja) * 2000-03-29 2001-12-14 Ibm Japan Ltd 処理システム、サーバ、処理端末、通信端末、処理方法、データ管理方法、処理実行方法、プログラム
US7379921B1 (en) * 2004-11-08 2008-05-27 Pisafe, Inc. Method and apparatus for providing authentication
US20100125510A1 (en) * 2008-11-17 2010-05-20 Smith Steven M System and method of conducting transactions using a mobile wallet system
US20110066550A1 (en) * 2009-09-16 2011-03-17 Shank Clinton L System and method for a secure funds transfer
KR20110039946A (ko) * 2009-10-13 2011-04-20 주식회사 아레오네트웍스 가맹점 무선 결제 방법 및 시스템과 이를 위한 기록매체
US20110166992A1 (en) * 2010-01-06 2011-07-07 Firethorn Holdings, Llc System and method for creating and managing a stored value account associated with a client unique identifier
US8380177B2 (en) * 2010-04-09 2013-02-19 Paydiant, Inc. Mobile phone payment processing methods and systems
JP5754751B2 (ja) * 2010-05-27 2015-07-29 グローバル ブルー エス．エー． 妥当性検査の方法及び装置
US8321345B2 (en) * 2010-06-02 2012-11-27 Visa International Service Association Trusted internal interface
JP2012048694A (ja) * 2010-08-26 2012-03-08 Zybox:Kk ワンクリック決済機能付オーダリング端末機

Also Published As

Publication number Publication date
EP2850572A4 (fr) 2016-01-06
CN104641388B (zh) 2018-07-10
BR112014028407A2 (pt) 2017-06-27
WO2013173339A1 (fr) 2013-11-21
JP2015525383A (ja) 2015-09-03
CN104641388A (zh) 2015-05-20

Similar Documents

Publication Publication Date Title
US10445723B2 (en) NFC-transaction processing systems and methods
US10395238B2 (en) Two step near field communication transactions
US10044412B1 (en) System and method for providing contactless payment with a near field communications attachment
CN106327175B (zh) 移动支付应用程序体系结构
CA2837491C (fr) Systeme et procede de chargement d'une carte de transaction et de traitement d'un remboursement sur un dispositif mobile
US9842356B2 (en) System, method, apparatus and computer program product for interfacing a multi-card radio frequency (RF) device with a mobile communications device
EP4120169A1 (fr) Procédé, dispositif et élément sécurisé pour réaliser une transaction financière sécurisée sur un dispositif
EP2850572A1 (fr) Systèmes et procédés de traitement de transaction de communication en champ proche (nfc)
Wu et al. Promoting collaborative mobile payment by using NFC-micro SD technology
KR20220066357A (ko) 다중 폐쇄 루프 보안 거래의 시스템 및 방법
CN114519580A (zh) 近距离通信的请求支付方法、支付方法、终端及存储介质

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20141215

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAX Request for extension of the european patent (deleted)
RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: PAYPAL, INC.

RA4 Supplementary search report drawn up and despatched (corrected)

Effective date: 20151207

RIC1 Information provided on ipc code assigned before grant

Ipc: G06Q 20/42 20120101AFI20151201BHEP

Ipc: H04B 5/02 20060101ALI20151201BHEP

Ipc: G06Q 20/36 20120101ALI20151201BHEP

Ipc: G06K 17/00 20060101ALI20151201BHEP

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20180508

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN

18W Application withdrawn

Effective date: 20210520