Source: https://patents.google.com/patent/US10062073B2/en
Timestamp: 2019-05-27 10:28:01
Document Index: 19185193

Matched Legal Cases: ['Application No. 2015201925', 'Application No. 2015201925', 'Application No. 2015201925', 'Application No. 2015201925', 'Application No. 2015201925', 'Application No. 15851256', 'Application No. 2']

US10062073B2 - System and method for providing a BLUETOOTH low energy mobile payment system - Google Patents
System and method for providing a BLUETOOTH low energy mobile payment system Download PDF
US10062073B2
US10062073B2 US14/469,230 US201414469230A US10062073B2 US 10062073 B2 US10062073 B2 US 10062073B2 US 201414469230 A US201414469230 A US 201414469230A US 10062073 B2 US10062073 B2 US 10062073B2
US14/469,230
US20160063476A1 (en
2014-08-26 Application filed by American Express Travel Related Services Co Inc filed Critical American Express Travel Related Services Co Inc
2014-08-26 Priority to US14/469,230 priority Critical patent/US10062073B2/en
2014-08-26 Assigned to AMERICAN EXPRESS TRAVEL RELATED SERVICES COMPANY, INC. reassignment AMERICAN EXPRESS TRAVEL RELATED SERVICES COMPANY, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BALDIE, David
2016-03-03 Publication of US20160063476A1 publication Critical patent/US20160063476A1/en
2018-08-28 Publication of US10062073B2 publication Critical patent/US10062073B2/en
A BLUETOOTH low energy mobile payments system may comprise a BLE beacon that is deployed at a merchant location. The BLE beacon may be associated with a specific merchant terminal. The BLE beacon may be configured to broadcast a unique beacon ID that is detectable by a user device. The user device may be configured to communicate the beacon ID to a payment system. In response to receiving the beacon ID, the user device may initiate a payment between a user and a merchant, via a user device and a merchant terminal.
The present disclosure relates to facilitating mobile payments, and more specifically, to systems and methods for creating a mobile payment system using BLUETOOTH low energy beacons.
Payment processing, point of sale devices, and payment capture systems are evolving. Some recent payment acquisition technologies have used near field communication, which includes communication protocols that allow user devices (e.g., smartphones and tablets) with appropriate communication equipment to communicate with point of sale devices. However, not all smartphones are equipped with NFC communication capabilities such as, for example, the iPhone®. Moreover, NFC communication protocols require a tap or bump by the smartphone to the point of sale device making it inconvenient for some users.
A system, method, and computer readable medium (collectively, the “System”) for facilitating wireless payments may comprise operations and/or steps performed by a computer based system including: receiving a beacon identifier associated with a Bluetooth low energy (“BLE”) beacon, and a customer identifier from a user device. The user device may be within a defined distance from the BLE beacon. The System may also include transmitting, to the user device, merchant information associated with the BLE beacon. The system may also include transmitting, to a merchant terminal, a request to make a payment from a user associated with the user device, and an image of the user. The System may include initiating a transaction based on transaction information received from a merchant. The transaction information may include a preliminary transaction amount. The System may also include receiving, from the user device, a user confirmation to authorize the transaction and a transaction amount.
In various embodiments, the transaction amount may be the preliminary transaction amount as modified by the user. The transaction information may include item information. The BLE beacon may be connected to a micro-registry.
In various embodiments, the user device may comprise an application. The application may be configured to recognize the BLE beacon and to create instructions for the request to make a payment. The BLE beacon may be detected by the user device. In response to the user device detecting the BLE beacon, the application may be automatically initiated. The system may also include receiving a merchant confirmation to confirm the transaction and the transaction amount.
FIG. 1A illustrates various exemplary modules and/or components for a payment system, in accordance with various embodiments;
FIG. 1B illustrates a BLUETOOTH low energy mobile payment system deployed at a merchant location with an associated merchant terminal, in accordance with various embodiments; and
FIG. 2 is a process flow for operating a BLUETOOTH low energy mobile payment system, in accordance with various embodiments.
The detailed description of exemplary embodiments herein makes reference to the accompanying drawings and pictures, which show various embodiments, by way of illustration. While these various embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, it should be understood that other embodiments may be realized and that logical and mechanical changes may be made without departing from the spirit and scope of the disclosure. Thus, the detailed description herein is presented for purposes of illustration only and not of limitation. For example, the steps recited in any of the method or process descriptions may be executed in any order and are not limited to the order presented. Moreover, any of the functions or steps may be outsourced to or performed by one or more third parties. Furthermore, any reference to singular includes plural embodiments, and any reference to more than one component may include a singular embodiment.
In various embodiments, and with reference to FIG. 1A, a payment system 100 may comprise a payment processing module 110, a user account system 120, and a merchant account system 130. Payment processing module 110 may be configured to receive requests, and/or initiate transactions between users and merchants. Payment processing module 110 may process, analyze, and/or otherwise execute the transactions causing monetary value to be transferred from the user to the merchant. Payment processing module 110 may be operatively coupled to and in electronic communication with user account system 120. User account system 120 may be any suitable system configured to manage user accounts. In this regard, user account system 120 may be any suitable bank, credit card or transaction account provider, and/or the like. User account system 120 may also be a portion of a stored value transaction account system. Merchant account system 130 may be any system (or portion of any system) that is configured to manage merchant transaction accounts. In this regard, merchant account system 130 may be configured to receive funds, money, credit and/or the like from user account system 120, in response to payment processing module 110 receiving transaction information.
In various embodiments, system 100 may further comprise a user gateway 140 and/or a merchant gateway 150. User gateway 140 may be configured to provide access for a user to payment processing module 110. Similarly, merchant gateway 150 may be configured to provide access for a merchant to payment processing module 110.
In various embodiments, and with reference to FIG. 1A and FIG. 1B, a merchant may provide and/or deploy a beacon 160. The beacon may be deployed at or near a merchant terminal 155. The beacon may be configured to broadcast a unique beacon identifier (“ID”). The beacon ID may be stored in system 100. Moreover, the beacon ID may be associated with a specific merchant, a specific merchant terminal 155, a particular merchant location, and/or the like. User device 145 may be configured to detect, monitor, and/or receive a transmission from BLE beacon 160. Transmission 165 may include the beacon ID. Examples of using BLE beacons, proximity based communications and dynamic proximity based e-commerce transactions, along with additional features and functions may be found in, for example, U.S. patent application Ser. No. 14/339,284 filed on Jul. 23, 2014 and entitled “SYSTEMS AND METHODS FOR PROXIMITY BASED COMMUNICATION” and U.S. patent application Ser. No. 14/284,817 filed on May 22, 2014 and entitled “SYSTEMS AND METHODS FOR DYNAMIC PROXIMITY BASED E-COMMERCE TRANSACTIONS”, which are hereby incorporated by reference in their entirety for any purpose.
In various embodiments, the beacon ID may comprise a globally unique identifier (“GUID”). The GUID may be an identifier created and/or implemented under the universally unique identifier standard. Moreover, the GUID may be stored as 128-bit value that can be displayed as 32 hexadecimal digits. The identifier may also include a major number, and a minor number. The major number and minor number may each be 16 bit integers. The unique combinations of major numbers and minor number may be assigned to BLE beacons and/or associated locations. As such, the identifier received by the user device and provided to the micro registry may be associated with a particular micro-location.
As used herein, a “micro-location” of a user may comprise a location of a user in relation to any energy consuming device. For example, the energy consuming device may comprise a high, medium, and/or low energy consuming device and/or any combination thereof. For example, the energy consuming device may be a low power and/or low energy consuming device. Such a device may be a BLUETOOTH device, such as a wireless beacon communicating using a low power or low energy BLUETOOTH communication standard (a “BLUETOOTH low energy beacon” or simply, a “BLE beacon”). However, in various embodiments, any type of low energy consuming device may be implemented with the systems described herein. For example, in various embodiments, any device (including any other BLE beacon) capable of communicating with a web-client and/or any other BLE beacon within three hundred meters of a BLE beacon may comprise a low energy consuming device. Thus, although the phrase “BLE beacon” is used herein with particular respect to a BLUETOOTH low energy consuming device, a BLE beacon may comprise any energy consuming device capable of communication with a web-client. In various embodiments, the low energy consuming device may capable of communication with a web-client to within approximately three hundred meters or less—that is, any device capable of communicating with a web-client within a micro-location of the web-client. As described above, a low energy consuming device (e.g., BLE beacon 150) may comprise any device capable of transmitting and/or receiving a signal wirelessly using a low power or low energy connection to a network. In various embodiments, such a signal may comprise a BLUETOOTH signal. A BLUETOOTH signal may comprise and/or utilize one or more internet protocol (“IP”) session connections. The IP session connections may enable a variety of piconet communication technologies. In various embodiments, particularly with regard IP version 6, a cryptographic key exchange protocol (symmetric and/or asymmetric) may be implemented. For example, a key management device may utilize IEEE Standard 1363.1-2013 for identity based cryptographic techniques that utilize pairings such that an encryption key may comprise one or more plain text strings (such as one or more email addresses).
Although the term “BLE beacon” is used herein in association with a BLUETOOTH communication protocol and/or signal, the phrase may refer to any communication protocol and/or any other “low energy” signal. As used herein, a “low energy signal” may comprise any signal capable of being received by a web-client within a range of approximately three hundred meters or less. In various embodiments, a BLE beacon may enable the discovery of a micro-location of a user. A micro-location may comprise any location of the user within, for example, user within a defined distance such as, within any suitable distance such as, for example, 10 meters to 10 centimeters of a BLE beacon.
The BLE beacons may be deployed in various physical locations including, for example, brick and mortar merchant locations. A merchant may use a third party service host to facilitate interactions between the merchant and the user. In this regard, the micro registry may help merchants engage users seamlessly, without regard to the service host employed by the merchant, because the service host will be seamlessly and instantly accessible through the micro registry. Moreover, the micro registry may reduce fragmentation of mobile and/or geo-location services.
As e-commerce and digital activities grow and the boundaries of the virtual marketplace and virtual world disappear, consumers are looking for ways to more easily conduct transactions, connect with merchants, obtain information about items, initiate transactions to make purchases, receive rewards, reverse items and/or the like. Providing a network that facilitates interactions between various service hosts, merchants, loyalty programs, acquirers, transaction account issuers, points of sale, payment services and/or the like allows the user to seamlessly connect with the merchant. This network also minimizes and/or eliminates the fragmentation that may occur, where service hosts are not accessible on the same network.
Phrases and terms similar to “business,” “service host” or “merchant” may be used interchangeably with each other and shall mean any person, entity, distributor system, software and/or hardware that is a provider, broker and/or any other entity in the distribution chain of goods or services. In this regard, the “business,” “service host” or “merchant” may facilitate a real world or virtual interaction, transaction, exchange of information between a supplier of an item and a user. This interaction or transaction may be trigger by a service request from a user in a micro registry.
In various embodiments, user device 145 may comprise a merchant application. The merchant application may be any suitable application configured to complete a payment with the merchant. User device 145 may also be configured to automatically detect transmission 165 from BLE beacon 160. In response to detecting transmission 165, user device 145 may automatically launch the merchant application.
In various embodiments, and with reference to FIGS. 1A-1B and FIG. 2, user device 145 may be capable of capturing a beacon ID associated with BLE beacon 160 in transmission 165. User device 145 may be capable of providing the beacon ID to system 100. Moreover, user device 145 may be connected to system 100. System 100 may be configured to receive a beacon ID associated with the BLE beacon and a customer and/or user identifier from user device 145 (step 210).
In various embodiments, user device 145 and/or system 100 may be configured to analyze transmission 165 from BLE beacon 160. This analysis may allow user device 145 and/or system 100 to determine the distance between user device 145 and BLE beacon 160. This distance may also be correlated to and/or may inform system 100, user device 145, merchant terminal 155, and/or the merchant of the user's proximity to the merchant terminal based on the user's proximity to BLE beacon 160. The distance may be determined by the signal strength that an application operating on user device 145 receives from BLE beacon 160. This signal strength may be translated to a distance. If there is something between BLE beacon 160 and user device 145 (e.g., a casing unit around BLE beacon 160 where it is integrated into merchant terminal 155) the signal strength may be reduced. As such, the system 100 may be adapted to accommodate any potential interference. For example, in operation user device 145 may need to be a pre-defined distance from BLE beacon 160 to initiate a payment. User device 145 and/or the merchant app operating on user device 145 may be configured with and/or capable of determining that pre-defined distance. The pre-defined distance may be for example, any suitable distance between 0 cm and 30 cm. Preferably, the predefined distance may be 0 cm to 20 cm. More preferably, the predefined distance may be 0 cm to 10 cm. Still more preferably, the predefined distance may be 0 cm to 5 cm.
In various embodiments, system 100 may transmit to user device 145 merchant information associated with BLE beacon 160. In this regard, system 100 may access a look-up table, micro-registry, and/or the like to determine the particular merchant location, payment terminal, micro-location, and/or the like associated with BLE beacon 160. The system 100 may quickly or substantially in real time, and in response to receiving the beacon ID and customer identifier, transmit merchant information to user device 145. Examples of a micro-registry and related systems may be found in, for example, U.S. patent application Ser. No. 14/454,452 filed on Aug. 7, 2014 and entitled “SYSTEM AND METHOD FOR PROVIDING A MICRO REGISTRY,” which is incorporated herein by reference.
In various embodiments, user device 145 and/or merchant terminal 155 may be passive. User device 145 and/or merchant terminal 155 may be configured to receive “push” messages from system 100 and/or merchant terminal 155. In this regard, user device 145 and/or merchant terminal 155 may passively wait for system 100. For example, user device 145 may have an amount on it, and the user may add, adjust, and/or include a tip in the amount. User device 145 may then confirm payment with system 100. User device 145 may call and/or transmit a confirmation to system 100. System 100 may then find merchant terminal 155, and perform a “push” down to merchant terminal 155. In this regard, merchant terminal 155 is not polling the payment system 100 to see if it has any messages that require action by merchant terminal 155.
In various embodiments, and in substantially real time and/or concurrently with the transmission of the beacon of the merchant information to user device 145, system 100 may transmit to merchant terminal 155 a request to make a payment from a user associated with user device 145 and an image of the user (Step 230). In this regard, system 100 may be capable of and/or may facilitate identification of the user associated with user device 145 via merchant terminal 155. System 100 may be configured to provide any suitable particularly identifying information about the user. For example, system 100 may provide an image of the user, a physical description of the user, and/or any other suitable identifying information. In this regard, an associate working for a merchant (e.g., an employee) operating merchant terminal 155 may be capable of determining that user associated with user device 145 is sufficiently close to merchant terminal 155 to make a payment. Moreover, particularly identifying a user may allow a merchant associate to facilitate payment by a particular user where there are multiple users with multiple user devices 145.
In various embodiments, system 100 may receive transaction details and/or transaction information from merchant terminal 155. This information may include, for example, a transaction amount, one or more items associated with the transaction, and/or any other suitable information including merchant information, manufacturer information, item information, and/or the like. In response to receiving this transaction information from the merchant and/or merchant terminal 155, system 100 may initiate a transaction based on the transaction information received from a merchant (step 240).
In various embodiments, system 100 may receive from user device 145 a user confirmation to authorize the transaction and/or a transaction amount (Step 250). System 100 may be configured to transmit to user device 145, preliminary transaction information including a preliminary transaction amount. A user associated with user device 145 may be configured to modify that transaction amount and/or adjust that transaction amount to provide for example, a gratuity, a tip and/or the like. In this regard, the user may adjust the preliminary transaction amount to provide a transaction amount.
In various embodiments, system 100 may also receive a merchant confirmation to confirm the transaction and the transaction amount (Step 260). For example, system 100 may transmit to merchant terminal 155 the transaction amount as modified and/or confirmed by the user. System 100 may further request that the merchant confirm the modified and/or user confirmed transaction amount via merchant terminal 150. In this regard, the confirmation process may allow a merchant to distribute a tip and/or gratuity to a merchant associate (e.g., an employee) or otherwise maintain accurate records of the various transactions the merchant conducts.
Terms and phrases similar to “associate” and/or “associating” may include tagging, flagging, correlating, using a look-up table or any other method or system for indicating or creating a relationship between elements, such as, for example, (i) a transaction account and (ii) an item (e.g., offer, reward, discount) (iii) a digital channel, (iv) a service request, (v) a service host, and/or the like. Moreover, the associating may occur at any point, in response to any suitable action, event, or period of time. The associating may occur at pre-determined intervals, periodic, randomly, once, more than once, or in response to a suitable request or action.
Terms and phases similar to “consumer,” “customer,” “user,” “account holder,” “account affiliate,” “cardmember,” or the like shall include any person, entity, business, government organization, business, software, hardware, machine associated with a transaction account, that buys merchant offerings offered by one or more merchants using the account and/or that is legally designated for performing transactions on the account, regardless of whether a physical card is associated with the account. For example, the cardmember may include a transaction account owner, a transaction account user, an account affiliate, a child account user, a subsidiary account user, a beneficiary of an account, a custodian of an account, and/or any other person or entity affiliated or associated with a transaction account.
In various embodiments, a transaction account may be may include any account that may be used to facilitate a financial transaction including, for example, a charge account, a credit account, a bank account (e.g., a checking or savings account), and/or the like. The transaction account may include a transaction instrument such as a charge card, credit card, debit card, awards card, prepaid card, telephone card, smart card, magnetic stripe card, bar code card, transponder, radio frequency card and/or the like having an account number, which cardholders typically present to Service Establishments (SEs), as part of a transaction, such as a purchase. An “account number”, as used herein, includes any device, code, number, letter, symbol, digital certificate, smart chip, digital signal, analog signal, biometric or other identifier/indicia suitably configured to allow the consumer to interact or communicate with the system, such as, for example, authorization/access code, personal identification number (PIN), Internet code, other identification code, and/or the like which is optionally located on card. The account number may be distributed and stored in any form of plastic, electronic, magnetic, radio frequency, wireless, audio and/or optical device capable of transmitting or downloading data from itself to a second device. A customer account number may be, for example, a sixteen-digit credit card number, although each credit provider has its own numbering system, such as the fifteen-digit numbering system used by American Express. Each company's credit card numbers comply with that company's standardized format such that the company using a sixteen-digit format will generally use four spaced sets of numbers, as represented by the number “0000 0000 0000 0000”. The first five to seven digits are reserved for processing purposes and identify the issuing bank, card type and etc. In this example, the last sixteenth digit is used as a sum check for the sixteen-digit number. The intermediary eight-to-ten digits are used to uniquely identify the customer.
In various embodiments, an account number may identify a consumer. In addition, in various embodiments, a consumer may be identified by a variety of identifiers, including, for example, an email address, a telephone number, a cookie id, a biometric, and the like.
The system may include or interface with any of the foregoing accounts, devices, and/or a transponder and reader in BLE communication with the transponder (which may include a fob), or communications between an initiator and a target enabled by short range communications protocols. Typical devices may include, for example, a key ring, tag, card, cell phone, wristwatch or any such form capable of being presented for interrogation. Moreover, the system, computing unit or device discussed herein may include a “pervasive computing device,” which may include a traditionally non-computerized device that is embedded with a computing unit. Examples may include watches, Internet enabled kitchen appliances, restaurant tables embedded with RF readers, wallets or purses with imbedded transponders, etc. Furthermore, a device or financial transaction instrument may have electronic and communications functionality enabled, for example, by: a network of electronic circuitry that is printed or otherwise incorporated onto or within the transaction instrument (and typically referred to as a “smart card”); a fob having a transponder and an RFID reader; and/or near field communication (NFC) technologies.
As used herein, the term “network” includes any cloud, cloud computing system or electronic communications system or method which incorporates hardware and/or software components. Communication among the parties may be accomplished through any suitable communication channels, such as, for example, a telephone network, an extranet, an intranet, Internet, point of interaction device (point of sale device, personal digital assistant (e.g., iPhone®, Palm Pilot®, Blackberry®), cellular phone, kiosk, etc.), online communications, satellite communications, off-line communications, wireless communications, transponder communications, local area network (LAN), wide area network (WAN), virtual private network (VPN), networked or linked devices, keyboard, mouse and/or any suitable communication or data input modality. Moreover, although the system is frequently described herein as being implemented with TCP/IP communications protocols, the system may also be implemented using IPX, Appletalk, IP-6, NetBIOS, OSI, any tunneling protocol (e.g. IPsec, SSH), or any number of existing or future protocols. If the network is in the nature of a public network, such as the Internet, it may be advantageous to presume the network to be insecure and open to eavesdroppers. Specific information related to the protocols, standards, and application software utilized in connection with the Internet is generally known to those skilled in the art and, as such, need not be detailed herein.
Phrases and terms similar to “transaction” may include any purchase, authorization, settlement, a record of charge (or “ROC”), record of transaction (“ROT”) and/or the like. Moreover, the transaction, information associated with the transaction, and/or a record associated with the transaction may comprise a unique identifier associated with a transaction. A transaction may, in various embodiments, be performed by one or more members using a transaction account, such as a transaction account associated with a transaction account such as, for example, a gift card, a debit card, a credit card, and the like. A record associated with the transaction may, in addition, contain details such as location, merchant name or identifier, transaction amount, transaction date, account number, account security pin or code, account expiry date, and the like for the transaction.
Encryption may be performed by way of any of the techniques now available in the art or which may become available—e.g., Twofish, RSA, El Gamal, Schorr signature, DSA, PGP, PKI, GPG (GnuPG), and symmetric and asymmetric cryptosystems.
The system and method may be described herein in terms of functional block components, screen shots, optional selections and various processing steps. It should be appreciated that such functional blocks may be realized by any number of hardware and/or software components configured to perform the specified functions. For example, the system may employ various integrated circuit components, e.g., memory elements, processing elements, logic elements, look-up tables, and the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices. Similarly, the software elements of the system may be implemented with any programming or scripting language with the various algorithms being implemented with any combination of data structures, objects, processes, routines or other programming elements. Further, it should be noted that the system may employ any number of conventional techniques for data transmission, signaling, data processing, network control, and the like. Still further, the system could be used to detect or prevent security issues with a client-side scripting language. For a basic introduction of cryptography and network security, see any of the following references: (1) “Applied Cryptography: Protocols, Algorithms, And Source Code In C,” by Bruce Schneier, published by John Wiley & Sons (second edition, 1995); (2) “Java Cryptography” by Jonathan Knudson, published by O'Reilly & Associates (1998); (3) “Cryptography & Network Security: Principles & Practice” by William Stallings, published by Prentice Hall; all of which are hereby incorporated by reference.
receiving, by a computer based system and from a Bluetooth low energy (“BLE”) beacon, a beacon identifier associated with the BLE beacon associated with a merchant, in response to a user device being within a defined distance from the BLE beacon;
receiving, by the computer based system and from a merchant application, a user identifier associated with the user device, in response to the user device being within the defined distance from the BLE beacon,
wherein the BLE beacon is located near a merchant terminal,
wherein the merchant application completes a payment with the merchant,
wherein the merchant application on the user device activates a Bluetooth radio that passively listens to Bluetooth broadcasts from the BLE beacon associated with the merchant,
wherein the beacon identifier is registered with a micro-registry, and
wherein the micro-registry comprises information for a plurality of beacon identifiers and a plurality of merchant systems;
analyzing, by the computer based system and in response to the receiving, the beacon identifier,
determining, by the computer based system, a micro-location of the BLE beacon within a facility of the merchant in response to and based on the analyzing and the information associated with the BLE beacon in the micro-registry;
transmitting, by the computer based system and to the user device and in response to the determining, merchant information associated with the BLE beacon;
transmitting, by the computer based system and to the merchant terminal associated with a merchant system and based on the merchant information, a request to conduct a transaction from a user associated with the user device, wherein the request includes an account number associated with the user and an image of the user,
wherein the image of the user is displayed on the merchant terminal;
receiving, by the computer based system and from the merchant terminal and in response to the request, a preliminary transaction amount to charge the user;
transmitting, by the computer based system and to the user device and in response to the receiving the preliminary transaction amount, the preliminary transaction amount;
receiving, by the computer based system and from the user device and in response to transmitting the preliminary transaction amount, a confirmation of a transaction amount,
wherein the transaction amount is the preliminary transaction amount as modified by the user; and
initiating, by the computer based system and based on the confirmation, the transaction for the transaction amount and using a transaction account.
2. The method of claim 1, wherein in response to detecting transmission from the BLE beacon, the user device automatically launches the merchant application.
3. The method of claim 1, wherein the preliminary transaction amount also includes item information.
4. The method of claim 1, further comprising receiving, by the computer based system, a merchant confirmation to confirm the transaction and the transaction amount.
5. The method of claim 1, wherein the micro-registry is in the cloud.
6. The method of claim 1, wherein the user device is a smart phone that includes the merchant application that is configured to recognize the BLE beacon and create instructions for the request to conduct the transaction.
7. The method of claim 6, wherein the BLE beacon is detected by the user device and the merchant application is automatically initiated in response to the user device detecting the beacon identifier.
8. The method of claim 1, wherein modification by the user of the preliminary transaction amount includes adding a tip amount to the preliminary transaction amount to obtain the transaction amount.
receiving, by the processor and from a Bluetooth low energy (“BLE”) beacon, a beacon identifier associated with the BLE beacon associated with a merchant, in response to a user device being within a defined distance from the BLE beacon;
receiving, by the processor and from a merchant application, a user identifier associated with the user device, in response to the user device being within the defined distance from the BLE beacon,
analyzing, by the processor and in response to the receiving, the beacon identifier,
determining, by the processor, a micro-location of the BLE beacon within a facility of the merchant in response to and based on the analyzing and the information associated with the BLE beacon in the micro-registry;
transmitting, by the processor and to the user device and in response to the determining, merchant information associated with the BLE beacon;
transmitting, by the processor and to the merchant terminal associated with a merchant system and based on the merchant information, a request to conduct a transaction from a user associated with the user device, wherein the request includes an account number associated with the user and an image of the user,
receiving, by the processor and from the merchant terminal and in response to the request, a preliminary transaction amount to charge the user;
transmitting, by the processor and to the user device and in response to the receiving the preliminary transaction amount, the preliminary transaction amount;
receiving, by the processor and from the user device and in response to transmitting the preliminary transaction amount, a confirmation of a transaction amount,
initiating, by the processor and based on the confirmation, the transaction for the transaction amount and using a transaction account.
10. The system of claim 9, wherein the preliminary transaction amount also includes item information.
11. The system of claim 9, further comprising receiving, by the processor, a merchant confirmation to confirm the transaction and the transaction amount.
12. The system of claim 9, wherein the micro-registry is in the cloud.
13. The system of claim 9, wherein the user device is a smart phone that includes the merchant application that is configured to recognize the BLE beacon and create instructions for the request to conduct the transaction.
14. The system of claim 13, wherein the BLE beacon is detected by the user device and the merchant application is automatically initiated in response to the user device detecting the beacon identifier.
15. An article of manufacture including a non-transitory, tangible computer readable storage medium having instructions stored thereon that, in response to execution by a computer-based system, cause the computer-based system to perform operations comprising:
receiving, by the computer based system and from a Bluetooth low energy (“BLE”) beacon, a beacon identifier associated with the BLE beacon associated with a merchant, in response to a user user device being within a defined distance from the BLE beacon;
16. The article of claim 15, wherein in response to detecting transmission from the BLE beacon, the user device automatically launches the merchant application.
17. The article of claim 15, further comprising receiving, by the computer based system, a merchant confirmation to confirm the transaction and the transaction amount.
18. The article of claim 15, wherein the micro-registry is in the cloud.
19. The article of claim 15, wherein the user device is a smart phone that includes the merchant application that is configured to recognize the BLE beacon and create instructions for the request to conduct the transaction.
20. The article of claim 19, wherein the BLE beacon is detected by the user device and the merchant application is automatically initiated in response to the user device detecting the beacon identifier.
US14/469,230 2014-08-26 2014-08-26 System and method for providing a BLUETOOTH low energy mobile payment system Active US10062073B2 (en)
US14/469,230 US10062073B2 (en) 2014-08-26 2014-08-26 System and method for providing a BLUETOOTH low energy mobile payment system
PCT/US2015/041940 WO2016032646A1 (en) 2014-08-26 2015-07-24 System and method for providing a bluetooth low energy mobile payment system
US16/109,046 US20180365677A1 (en) 2014-08-26 2018-08-22 Transactions using a bluetooth low energy beacon
US16/109,046 Continuation US20180365677A1 (en) 2014-08-26 2018-08-22 Transactions using a bluetooth low energy beacon
US20160063476A1 US20160063476A1 (en) 2016-03-03
US10062073B2 true US10062073B2 (en) 2018-08-28
ID=55400287
US14/469,230 Active US10062073B2 (en) 2014-08-26 2014-08-26 System and method for providing a BLUETOOTH low energy mobile payment system
US16/109,046 Pending US20180365677A1 (en) 2014-08-26 2018-08-22 Transactions using a bluetooth low energy beacon
US (2) US10062073B2 (en)
WO (1) WO2016032646A1 (en)
US20160092880A1 (en) * 2014-09-26 2016-03-31 Apriva, Llc System and method for facilitating a purchase transaction using a merchant device beacon
US20160180319A1 (en) * 2014-12-22 2016-06-23 Apriva, Llc System and method for facilitating an online transaction with a mobile device
US10050942B2 (en) 2015-03-17 2018-08-14 Ca, Inc. System and method of mobile authentication
US10089631B2 (en) 2015-03-18 2018-10-02 Ca, Inc. System and method of neutralizing mobile payment
US20170032354A1 (en) * 2015-07-27 2017-02-02 Paypal, Inc. Wireless communication beacon and gesture detection system
US20040098332A1 (en) 2002-11-15 2004-05-20 Haim Dvir Method of sales and marketing primarily involving catalogue advertising, sealed bidding type auctions
US20050159863A1 (en) 2004-01-16 2005-07-21 Howard William B. Method and system to transfer and to display location information about an object
US20060047546A1 (en) 2004-09-01 2006-03-02 Richard Taylor Computer-based retail data management system and method thereof
US7010267B2 (en) 2001-03-19 2006-03-07 Koninklijke Philips Electronics N.V. Arrangement with beacon for providing information service
US7147149B2 (en) 2002-11-19 2006-12-12 Safetzone Technologies Corporation Cashless spending system and method
US20070061216A1 (en) 2005-09-15 2007-03-15 Microsoft Corporation Budget-dependent pseudo bid in auction
US7254388B2 (en) 2004-07-13 2007-08-07 Electronics And Telecommunications Research Institute System for MS-assisted location trigger, and service methods thereof
US20080109317A1 (en) * 2006-10-26 2008-05-08 Gurvinder Singh Wireless dissemination of environment aware information
US20100082446A1 (en) 2008-10-01 2010-04-01 Johan Hjelm Trusted auctions
US20100180009A1 (en) 2009-01-14 2010-07-15 Michael Callahan Anonymous Digital Identification
US20100320266A1 (en) * 2009-06-23 2010-12-23 At&T Mobility Ii Llc Devices, Systems and Methods for Wireless Point-of-Sale
US7926717B2 (en) 2005-11-08 2011-04-19 At&T Intellectual Property I, L.P. Systems, methods and computer program products for wirelessly preprocessing a transaction while in a queue for a point-of-transaction
US20110231272A1 (en) 2010-03-16 2011-09-22 App Masters Llc Retail mobile point-of-sale (POS) software application and retail middleware software application
US8032414B2 (en) 2007-06-12 2011-10-04 Gilbarco Inc. System and method for providing receipts, advertising, promotion, loyalty programs, and contests to a consumer via an application-specific user interface on a personal communication device
US20120022944A1 (en) 2002-10-23 2012-01-26 Matthew Volpi System and method of a media delivery services platform for targeting consumers in real time
US8271322B2 (en) 2008-07-22 2012-09-18 Distinctive Technologies Llc Customer experience management system
US8285588B2 (en) 1999-06-23 2012-10-09 Signature Systems, LLC. Method and system for providing rewards to a portable computing device at the point of sale
US8295835B2 (en) 2000-02-09 2012-10-23 Apriva, Llc System and method for registration for application program deployment
US20120324242A1 (en) 2011-06-16 2012-12-20 OneID Inc. Method and system for fully encrypted repository
US8369842B2 (en) 2008-09-08 2013-02-05 Proxicom Wireless, Llc Exchanging identifiers between wireless communication to determine further information to be exchanged or further services to be provided
US8423048B2 (en) 2008-01-08 2013-04-16 Global Alert Network, Inc. Mobile alerting network
US8483714B2 (en) 2010-10-06 2013-07-09 Sony Corporation Method and apparatus for identification of local beacon systems
US20130204697A1 (en) 2011-09-15 2013-08-08 Coupons.Com Incorporated Checkout-based distributed of digital promotions
US20130217332A1 (en) 2012-02-22 2013-08-22 Qualcomm Incorporated Platform for Wireless Identity Transmitter and System Using Short Range Wireless Broadcast
US8533000B1 (en) 1999-12-30 2013-09-10 Jpmorgan Chase Bank, N.A. System and method for integrated customer management
US8538389B1 (en) 2010-07-02 2013-09-17 Mlb Advanced Media, L.P. Systems and methods for accessing content at an event
US8534551B2 (en) 2005-08-26 2013-09-17 Clayco Research Limited Liability Company System and method for issuing digital receipts for purchase transactions over a network
US20130251216A1 (en) * 2012-03-23 2013-09-26 Microsoft Corporation Personal Identification Combining Proximity Sensing with Biometrics
US20130325891A1 (en) 2012-05-30 2013-12-05 Rafeh Masood Methods and systems for connected sales associate services
US8618932B2 (en) 2011-03-18 2013-12-31 Microsoft Corporation Device location detection
US20140046794A1 (en) 2012-08-07 2014-02-13 Ebay Inc Shopping assistant
US20140108108A1 (en) 2012-10-17 2014-04-17 Groupon, Inc. Consumer presence based deal offers
US8740064B2 (en) 2011-04-08 2014-06-03 Blackberry Limited Payment processing system including mobile wireless communications device to send a payment confirmation to a transaction terminal and associated methods
WO2014106207A1 (en) 2012-12-31 2014-07-03 Ebay Inc. Dongle facilitated wireless consumer payments
US8774753B2 (en) 2009-03-03 2014-07-08 Mobilitie LLC System and method for direct communication between wireless communication devices
US8818268B2 (en) 2011-06-24 2014-08-26 Kabushiki Kaisha Toshiba Content data distribution system, content data delivery method, and semiconductor device
US20150073980A1 (en) * 2013-09-06 2015-03-12 Ebay Inc. Bluetooth low energy (ble) pre-check in
US9015277B1 (en) 2013-07-26 2015-04-21 Codebroker, Llc Delivering promotions associated with user profiles through multiple digital channels associated with the user profiles
US20150120558A1 (en) * 2013-10-29 2015-04-30 Cubic Corporation Fare collection using wireless beacons
US20150140982A1 (en) * 2013-11-15 2015-05-21 Richard Postrel Method and system for pre and post processing of beacon id signals
WO2015102889A1 (en) 2014-01-02 2015-07-09 Ebay Inc. Proxied push notifications based on user interaction
US20150220924A1 (en) 2014-02-04 2015-08-06 Outsite Networks, Inc. Method and system for linking a customer identity to a retail transaction
US20150230045A1 (en) * 2014-02-10 2015-08-13 Jvl Ventures, Llc Mobile devices, methods, and computer program products for prioritizing data sets
US20150248702A1 (en) 2014-03-03 2015-09-03 Ebay Inc. Proximity-based visual notifications
US20150302412A1 (en) 2014-04-17 2015-10-22 Google Inc. Online bank transfer transactions
US20150339655A1 (en) 2014-05-22 2015-11-26 American Express Travel Related Services Company, Inc. Systems and methods for dynamic proximity based e-commerce transactions
US20150363861A1 (en) 2014-06-13 2015-12-17 Sailthru, Inc, System and method for improved personalization using beacon technology
US20150381664A1 (en) 2014-06-27 2015-12-31 American Express Travel Related Services Company, Inc. System and Method for Connectivity Contextual Services Local Online Experience
US20150379581A1 (en) 2014-06-27 2015-12-31 American Express Travel Related Services Company, Inc. System and method for contextual services experience
US20150379650A1 (en) * 2014-06-27 2015-12-31 Ebay Inc. Communication of orders and payments in a drive through using wireless beacons
US20160019536A1 (en) 2012-10-17 2016-01-21 Royal Bank Of Canada Secure processing of data
US20160019526A1 (en) 2014-07-17 2016-01-21 Ebay Inc. Drive through monitoring using wireless beacons
US20160063476A1 (en) 2014-08-26 2016-03-03 American Express Travel Related Services Company, Inc. System and method for providing a bluetooth low energy mobile payment system
US9326226B2 (en) * 2014-08-08 2016-04-26 Microsoft Technology Licensing, Llc Beacon discovery service
US20160267480A1 (en) 2015-03-12 2016-09-15 Paypal Inc. Replaying Tokenized Payment Transactions
US20170091765A1 (en) 2015-09-30 2017-03-30 Bank Of America Corporation Non-intrusive geo-location determination associated with transaction authorization
US9665881B1 (en) 2012-05-04 2017-05-30 Amazon Technologies, Inc. Physical store online shopping control
2014-08-26 US US14/469,230 patent/US10062073B2/en active Active
2015-07-24 WO PCT/US2015/041940 patent/WO2016032646A1/en active Application Filing
2018-08-22 US US16/109,046 patent/US20180365677A1/en active Pending
US8688460B1 (en) 1999-12-30 2014-04-01 Jpmorgan Chase Bank, N.A. System and method for integrated customer management
WO2015134947A1 (en) 2014-03-03 2015-09-11 Ebay Inc. Proximity-based visual notifications
"U.S. Appl. No. 14/284,817, filed May 22, 2014 and entitled Systems and Methods for Dynamic Proximity Based E-Commercetransactions".
"U.S. Appl. No. 14/318,091, filed Jun. 27, 2014 and entitled System and Method for Contextual Services Experiencetransactions".
"U.S. Appl. No. 14/995,052, filed Jan. 13, 2016 and entitled System and Method for Creating Administering Electroniccredentialscredentials".
Advisory Action dated Jan. 25, 2017 in U.S. Appl. No. 14/284,817.
Advisory Action dated Jul. 13, 2017 in U.S. Appl. No. 14/454,452.
Advisory Action dated Jun. 12, 2017 in U.S. Appl. No. 14/339,284.
Advisory Action dated Jun. 12, 2018 in U.S. Appl. No. 14/454,452.
Advisory Action dated Mar. 27, 2018 in U.S. Appl. No. 14/515,813.
Advisory Action dated Nov. 7, 2017 in U.S. Appl. No. 14/318,091.
Anonymous, Swirl Delivers First End-to-End In-Store Mobily Marketing Platform for Major Retailers, Oct. 17, 2013, PR Newsire. (Year: 2013).
Apple, Inc., "Getting Started with iBeacon Version 1.0", Jul. 2, 2014, entire document. *
Examination Report dated Aug. 3, 2016 in Australian Application No. 2015201925.
Examination Report dated Feb. 24, 2017 in Australian Application No. 2015201925.
Examination Report dated Feb. 26, 2016 in Australian Application No. 2015201925.
Examination Report dated Jan. 23, 2017 in Australian Application No. 2015201925.
Examination Report dated Nov. 22, 2016 in Australian Application No. 2015201925.
Extended European Search Report dated Jun. 16, 2017 in European Application No. 15851256.6.
Final Office Action dated Dec. 29, 2017 in U.S. Appl. No. 14/339,284.
Final Office Action dated Jan. 24, 2018 in U.S. Appl. No. 14/515,813.
Final Office Action dated Jun. 14, 2018 in U.S. Appl. No. 14/318,091.
Final Office Action dated Mar. 16, 2017 in U.S. Appl. No. 14/454,452.
Final Office Action dated Mar. 28, 2017 in U.S. Appl. No. 14/339,284.
Final Office Action dated Nov. 10, 2016 in U.S. Appl. No. 14/284,817.
Final Office Action dated Sep. 12, 2017 in U.S. Appl. No. 14/318,091.
International Preliminary Report on Patentabiliy dated Feb. 25, 2016 in Application No. PCT/US2015/041940.
International Preliminary Report on Patentabiliy dated Mar. 28, 2016 in Application No. PCT/US2015/051693.
International Search Report and Written Opinion dated Dec. 30, 2015 in Application No. PCT/US2015/051693.
International Search Report and Written Opinion dated Oct. 23, 2015 in Application No. PCT/US2015/041940.
Non-Final Office Action dated Feb. 9, 2018 in U.S. Appl. No. 14/318,091.
Non-Final Office Action dated Mar. 9, 2018 in U.S. Appl. No. 14/995,052.
Non-final Office Action dated May 23, 2018 in U.S. Appl. No. 14/339,284.
Office Action dated Apr. 25, 2016 in Canadian Application No. 2,888,085.
Office Action dated Aug. 12, 2016 in U.S. Appl. No. 14/454,452.
Office Action dated Aug. 16, 2017 in U.S. Appl. No. 14/515,813.
Office Action dated Jul. 14, 2017 in U.S. Appl. No. 14/339,284.
Office Action dated Jul. 7, 2016 in U.S. Appl. No. 14/284,817.
Office Action dated Mar. 24, 2017 in U.S. Appl. No. 14/318,091.
Office Action dated Nov. 14, 2017 in U.S. Appl. No. 14/284,817.
Office Action dated Nov. 17, 2016 in U.S. Appl. No. 14/339,284.
Office Action dated Oct. 2, 2017 in U.S. Appl. No. 14/454,452.
Pocket-lint, Apples iBeacons explained: What it is and why it matters, retrieved from internet on Feb. 21, 2017, http://web.archive.org/web/20130925141212/http://www.pocket-lint.com/news/123730-apple-sibeacons-explained-what-it-is-and-why-it-matters> published on Sep. 25, 2013 as per WaybackMachine, 10 pages.
U.S. Appl. No. 14/339,284, filed Jul. 23, 2014 and entitled Systems and Methods for Proximity Based Communication.
U.S. Appl. No. 14/454,452, filed Aug. 7, 2014 and entitled System and Method for Providing a Micro Registry.
U.S. Appl. No. 15/154,106, filed May 13, 2016 and entitled Systems and Methods for Contextual Services Across Platforms Based on Selectively Shared Information.
U.S. Appl. No. 15/237,141, filed Aug. 15, 2016 and entitled Systems and Methods for Contextual Services Using Voice Personal Assistants.
U.S. Appl. No. 15/338,654, filed Oct. 31, 2016 and entitled Contextual Identification and Information Security.
U.S. Appl. No. 15/442,945, filed Feb. 27, 2017 and entitled Contextual Injection.
USPTO, Advisory Action dated Feb. 15, 2018 in U.S. Appl. No. 14/339,284.
USPTO, Advisory Action dated Mar. 27, 2018 in U.S. Appl. No. 14/515,813.
USPTO, Final Office Action dated Apr. 20, 2018 in U.S. Appl. No. 14/454,452.
US20160063476A1 (en) 2016-03-03
WO2016032646A1 (en) 2016-03-03
US20180365677A1 (en) 2018-12-20
US8235285B1 (en) 2012-08-07 Systems and methods for gesture-based interaction with computer systems
US9747598B2 (en) 2017-08-29 Dynamic security code push
US20140090045A1 (en) 2014-03-27 Systems and methods for facilitating login aid functionality in mobile commerce
CN105493484A (en) 2016-04-13 Systems and methods for enabling additional devices to check in to bluetooth low energy (BLE) beacons
US20150120504A1 (en) 2015-04-30 Systems and methods for completion of item delivery and transactions using a mobile beacon
US8880881B2 (en) 2014-11-04 Secure communications between devices
US8874913B1 (en) 2014-10-28 Secure communications between devices using a trusted server
CA2849324A1 (en) 2013-03-28 Systems and methods for contactless transaction processing
US9824504B2 (en) 2017-11-21 Mobile card processing using multiple wireless devices
US20130304637A1 (en) 2013-11-14 Fraud control integrated form filling tool
US9098842B2 (en) 2015-08-04 Smart phone system and method
JP6383804B2 (en) 2018-08-29 Information push method, online payment methods and pos terminal
US8770478B2 (en) 2014-07-08 Payment processing with automatic no-touch mode selection
US10163122B2 (en) 2018-12-25 Purchase instructions complying with reservation instructions
US9785920B2 (en) 2017-10-10 Acquisition of card information to enhance user experience
US20180174134A1 (en) 2018-06-21 Augmented reality card activation
WO2013165759A1 (en) 2013-11-07 Quick transaction completion using mobile device
US9818159B2 (en) 2017-11-14 Systems and methods for expense management
US20140249939A1 (en) 2014-09-04 Techniques for mobile transaction processing
US9928358B2 (en) 2018-03-27 Methods and systems for using transaction data to authenticate a user of a computing device
US20140222663A1 (en) 2014-08-07 Group payment
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BALDIE, DAVID;REEL/FRAME:033613/0803