Patent ID: 12229769

Like reference numerals refer to corresponding parts throughout the several views of the drawings.

DETAILED DESCRIPTION

Disclosed herein is a payment processing system or, more specifically, a mobile-device-to-machine payment processing system for processing transactions over a non-persistent network connection. The mobile-device-to-machine payment processing system disclosed herein focuses on the unattended retail space (e.g., a payment accepting unit120, sometimes also herein called a “machine120”). More specifically, the mobile-device-to-machine payment processing system disclosed herein allows a user (having a mobile device150with a mobile application140thereon) to make a cashless purchase from a payment accepting unit120(having an adapter module100associated therewith).

The mobile-device-to-machine payment processing system described herein can be implemented with one or more of the following features: easy installation feature, a non-persistent network connection feature; a manual (swipe to pay) mode feature; a hands-free mode feature; and a multiple vending transactions (multi-vend) feature.

Easy Installation: Installation is very easy, requires no tools, requires no configuration, and takes as little as 30 seconds. This is accomplished by using an adapter module100(sometimes also herein called “payment module100”) such as an in-line dongle (a hardware device with software thereon) design for in-line insertion within a multi-drop bus (MDB) of a payment accepting unit120(e.g., a vending machine) (sometimes also herein called ‘the machine120”). Installation is as simple as “powering down” (turning off) the machine120, identifying the “wire” that connects with a payment receiving mechanism (e.g., the coin mechanism), disconnecting the wire (so that there are two loose ends, such as a male connection end or adapter of an MDB and a female connection end or adapter of an MDB), plugging (inserting) the adapter module100in serial (“in-line”) with the wire (e.g., connecting the MDB female adapter to a male adapter of the adapter module100and connecting the MDB male adapter to a female adapter of the adapter module100), tucking the wire and the installed adapter module100back into position, and “powering up” (turning on) the machine120. Most vending machines made since 1995 have this industry standard MDB technology that would allow this easy 30-second installation. On machines without MDB technology, the adapter module100can be configured or designed to work with other serial protocols or activate a switch. In essence the adapter module100simulates establishing payment on payment accepting unit120in much the same manner as other alternative forms of payment (e.g., cash).

Non-persistent Network Connection: Although payment accepting units (or “machines”) that accept only cash (e.g., paper currency and coins) may not require a connection (persistent or non-persistent) to a network, traditional payment accepting units that accept cashless payments (e.g., credit cards, debit cards, and alternative mobile device payment methods using, for example, smart phones) require a persistent connection to a network (wired or wireless) to facilitate the cashless payments. In other words, without a persistent (ongoing or accessible on demand) network connection, traditional payment accepting units cannot accept cashless payments. Most traditional payment accepting units that accept cashless payments include the technology to accomplish this persistent network connection that allows them to connect to a remote server. If the network connection to a traditional machine is temporarily interrupted, cashless payments will be temporarily unavailable. If the machine is located in a location where no network connection is available, cashless payments is not possible. In addition to using a mobile device150as an intermediary between the payment accepting units120and the server130, the mobile-device-to-machine payment processing system described herein minimizes (i.e., the manual mode) or eliminates (i.e., the hands-free mode) user interaction with the mobile device150. Further, in some implementations, the mobile-device-to-machine payment processing system described herein facilitates the acceptance of cashless payments without requiring any network connection near the payment accepting unit120. In some implementations, when the mobile-device-to-machine payment processing system described herein is located in a remote location where network connection is unavailable, the mobile-device-to-machine payment processing system, therefore, can still accept cashless payments.

Manual (Swipe-to-Pay) Mode: Using a “swipe-to-pay” feature (or just “swipe”) refers to a user's action implemented on his/her mobile device150where he/she quickly brushes his/her finger (or other pre-determined interaction) on the mobile device's touch screen152(FIGS.10A-10D) or other input devices associated with the mobile device150. From the user's perspective, when the user is within range, a pre-installed mobile application140automatically connects to the payment accepting unit120(e.g., a vending machine). The mobile application140might display (on the touch screen152) a prepaid balance that the user “swipes” to transfer payment to the payment accepting unit120. The user could observe the transferred funds on the touch screen152of the mobile device150and/or on the display122,124(FIG.19) of the payment accepting unit120. The transaction is completed just as if cash was inserted in the machine120with the user inputting his selection on the payment accepting unit120and the payment accepting unit120dispensing the product or service. After the selection is made, the change is returned to the mobile device150and this may be shown on the touch screen152of the mobile device150.

Hands-Free Mode: A “hands-free pay” feature (or just “hands-free”) would most likely be used with “favorite” payment accepting units120(e.g., a frequently used vending machine at a user's work or school). From the user's perspective, he/she would approach the favorite payment accepting unit120and notice that the display122,124(FIG.19) of the payment accepting unit120shows funds available, he/she would select the product or service using the payment accepting unit's input mechanisms (e.g., buttons126or a touch screen display124shown inFIG.19), and he/she would retrieve dispensed services or products. It would be that simple. More specifically, when the user is within range, a pre-installed mobile application140automatically connects to the payment accepting unit120(e.g., a vending machine). The user may leave the mobile device150in a pocket, purse, briefcase, backpack, or other carrier. As the user approaches the payment accepting unit120and is in approximately “arm's-length” distance (e.g., 3 to 5 feet) of the payment accepting unit120, the user could observe the transferred funds on the display122,124(FIG.19) of the payment accepting unit120. The transaction is completed just as if cash was inserted into the payment accepting unit120with the user inputting his/her selection on the payment accepting unit120and the payment accepting unit120dispensing the product or service. After the selection is made, the change is returned to the mobile device150.FIG.3details when the hands-free mode would be available.

Multiple Vending Transactions (Multi-Vend): Both the manual and hands-free modes could be used multiple times in sequence (implemented, for example, as a loop) so that a user may make multiple purchases. After making his/her first selection and receiving his product (or service), the user would observe that additional funds were available on the display122,124(FIG.19) on the payment accepting unit120. He/she could make another selection (or multiple selections) and receive additional product(s) (or service(s)). More specifically, the display122,124(FIG.19) may reset as if the transaction is complete, but then, because the user is still standing in range, the mobile application140would send another credit to the payment accepting unit120, allowing for a second purchase. When the user walks away, the system clears (e.g., returns unused funds to the application140on the mobile device150).

The features described above, alone or in combination with other features described herein will revolutionize the hundred billion dollar automated retail industry. The hardware is very low cost and there are no reoccurring fees because no cellular connection is required on the machine120. Using the mobile-device-to-machine payment processing system described herein, operators of machines120can increase frequency of visits by purchasers and items sold with each visit.

The mobile-device-to-machine payment processing system described herein may be implemented as an apparatus, system, and/or method for enabling payments to a machine120via a mobile device150. The mobile-device-to-machine payment processing system may be better understood with reference to the drawings, but the shown mobile-device-to-machine payment processing system is not intended to be of a limiting nature.

Definitions

Before describing the mobile-device-to-machine payment processing system and the figures, some of the terminology should be clarified. Please note that the terms and phrases may have additional definitions and/or examples throughout the specification. Where otherwise not specifically defined, words, phrases, and acronyms are given their ordinary meaning in the art. The following paragraphs provide some of the definitions for terms and phrases used herein.

Adapter Module100: As shown inFIGS.1and2, the adapter module100(sometimes also herein called the “payment module100”) is a physical device that is installed in a machine120(a payment accepting unit120). The shown adapter module100is an in-line dongle (a hardware device with software thereon) device that may be inserted in-line within a multi-drop bus (MDB) of a machine120. The adapter module100bridges the communication between the machine120and a mobile device150. Although described as a unique component, it should be noted that the adapter module100could be implemented as a plurality of devices or integrated into other devices (e.g., components of a machine120). In its unique component form, the adapter module100can be easily inserted into a machine120so that the machine120is able to perform new features with the assistance of the adapter module100.FIG.20shows components associated with the adapter module100. As shown inFIG.20, the communications unit770of the adapter module100includes short-range communication capability776(e.g., Bluetooth mechanisms). The shown example may be divided into multiple distinct components that are associated with each other or the example may be incorporated into or drawn from other technology (e.g., a computer or a payment accepting unit) as long as the components are associated with each other.

Mobile Device150and Application140(also referred to as a “mobile application,” “mobile app,” or “app”): In general, a mobile device150may be a user's personal mobile device150. The mobile device150(with a mobile application140thereon) acts as a communication bridge between the adapter module100(associated with a payment accepting unit120) and the server130. The mobile device150and the application140, however, are not “trusted” in that the communications (transmissions) it passes are encrypted. Encrypted (secured) communications are undecipherable (unencryptable, unreadable, and/or unusable) by the mobile device150. This keeps the communications passed between the adapter module100and the server130secured and safe from hacking. Mobile devices include, but are not limited to smart phones, tablet or laptop computers, or personal digital assistants (PDAs), smart cards, or other technology (e.g., a hardware-software combination) known or yet to be discovered that has structure and/or capabilities similar to the mobile devices described herein. The mobile device150preferably has an application (e.g., the application140) running on it. The term “app” is used broadly to include any software program(s) capable of implementing the features described herein.FIGS.10A-10Dshow user interfaces for the application140displayed by the mobile device150. It should be noted that the phrase “mobile device” can be assumed to include the relevant app unless specifically stated otherwise. Similarly, it should be noted that an “app” can be assumed to be running on an associated mobile device unless specifically stated otherwise.FIG.21shows components associated with the mobile device150. The shown example may be divided into multiple distinct components that are associated with each other or the example may be incorporated into or drawn from other technology (e.g., the cell phone itself) as long as the components are associated with each other.

Payment accepting unit120(or Machine120): A payment accepting unit120(or the machine120) is equipment that requires payment for the dispensing of an product and/or service. Payment accepting units120may be vending machines, parking meters, toll booths, laundromat washers and dryers, arcade games, kiosks, photo booths, toll booths, transit ticket dispensing machines, and other known or yet to be discovered payment accepting units120. Some payment accepting units120can accept cashless payments (payments other than cash (paper currency and coins)) by accepting payment from, for example, credit cards, debit cards, and mobile devices.

Network Connections: For purposes of this discussion, a persistent network connection is a wired or wireless communications connection that is ongoing (e.g., a dedicated connection, a dedicated online connection, and/or a hardwired connection) or accessible on demand (e.g., the ability for the machine to make a temporary connection to a server or the ability for the user to contact a server from his mobile device). Typically the persistent network connection has been conducted over “long-range communication technology” or “long-range communication protocol” (e.g., hardwired, telephone network technology, cellular technology (e.g., GSM, CDMA, or the like), Wi-Fi technology, wide area network (WAN), local area network (LAN), or any wired or wireless communication technology over the Internet that is known or yet to be discovered). Traditionally, machines that accept payment other than cash require a persistent (ongoing or accessible on demand) connection to a network to facilitate payment. This is true for machines that accept, for example, credit cards and debit cards. The payment accepting units120described herein do not require a traditional persistent network connection. The user's mobile device150acts as a communication bridge between the adapter module100and the server130. Communications between user mobile devices150and the servers (e.g., a system management server130and/or a funding source server160) take place using long-range communication technology. Communications between user mobile devices150and the adapter module100of the payment accepting unit120take place using “short-range communication technology” or “short-range communication protocol” (e.g., Bluetooth (such as Bluetooth 4.0, Bluetooth Smart, Bluetooth Low Energy (BLE)), near-field communication (NFC), Ultra Wideband (UWB), radio frequency identification (RFID), infrared wireless, induction wireless, or any wired or wireless technology that could be used to communicate a small distance (approximately a hundred feet or closer) that is known or yet to be discovered). Therefore, neither the adapter module100nor the payment accepting unit120requires a traditional persistent long-range wireless network connection. The communications technology shown in the figures may be replaced with alternative like communications technology and, therefore, specific shown communications technologies are not meant to be limiting. For example, Wi-Fi technology could be replaced with another long-range communication technology.

Server: A server is the host processing server that may be operated by the company running the payment processing system. For each user, the server130preferably maintains at least one “virtual wallet” having at least one “balance” (which can be $0) of designated funds for which the server130keeps an accounting. The balance may represent, for example, “cash” or it may be a “promotional value” that represents funds that may be spent under certain circumstances. If these funds begin to be depleted, the user may be notified (e.g., via the application140on the mobile device150) that additional funds need to be designated and/or transferred. Alternatively, funds from other sources (e.g., the funding source server160) may be automatically transferred to restore a predetermined balance. The balance may also be increased based on a promotion (e.g., points earned or coupons). As shown inFIG.22, the server includes appropriate processors950, memory960(which would keep an accounting of the user's balance in a manner similar to a gift card), and communication systems970. As shown inFIG.22, the communications unit970of the server130includes long-range communication capability972(e.g., cellular technology and/or Wi-Fi mechanisms). The server130also includes a security unit955for encrypting and decrypting messages. The server130receives an authorization request (sometimes also herein called an “AuthRequest”) from the adapter module100(via a mobile device150) and, if funds are available, returns an authorization grant (sometimes also herein called an “AuthGrant” or an “authorization grant token”) for funds.FIG.22shows components associated with the server130. The shown example may be divided into multiple distinct components that are associated with each other or the example may be incorporated into or drawn from other technology (e.g., a computer or a main frame) as long as the components are associated with each other.

Advertise Presence: Each adapter module100advertises its presence by broadcasting signals (advertising broadcast signals) to mobile devices in the zones102,104,106. Each adapter module100can listen to other adapter modules' advertisements.

Received Signal Strength Indicator (RSSI): The adapter module100may have a self-calibrating signal strength to determine zone thresholds (e.g., a payment zone threshold and an authentication zone threshold). At the time the user selects an item (product or service) from the payment accepting unit120, the Received Signal Strength Indicator (RSSI) is logged. At this moment, it is presumed the user is within “arm's-length” (which may be a predetermined length approximating the distance of a user standing in front of a machine for the purpose of making a purchase) from the payment accepting unit120. A mathematical computation (i.e., In-Range Heuristics) is conducted to derive the optimal RSSI threshold at which point payment should be triggered by an application140on a mobile device150. The threshold may be payment accepting unit specific and can vary over a period of time. This optimal zone threshold is preferably reported to the mobile device150during an initial handshake.

In-Range Heuristics: A mathematical computation that determines the RSSI threshold to determine when a user is in the authorization zone104and/or the payment zone102. This computation can take into consideration numerous historical data points as well as transaction specific information such as which the mobile device150is being used, payment accepting unit type, among other factors. Preferably the RSSI is logged while the user is making his selection (this is the one time in the entire process that the user definitely will be “in range” (e.g., they will be arm's length from the machine120because they are physically interacting with the machine120). The type of user mobile device150, accelerometer data (e.g., is the user moving or stationary), and/or other information may also be logged while the user is making his selection. The adapter module100can give a reference RSSI for the payment zone102for the machine120, and the application140can make a +/− adjustment based on the specific mobile device150on which it is installed. Over a period of time, the payment processing system continues to improve itself based on additional data points.

Authorization Request (“AuthRequest:): When a user enters the authorization zone104, the mobile device150notifies the adapter module100and the adapter module100sends a secured authorization request (e.g., the encrypted authorization request) as a “message” (also referred to as a communication or transmissions) to the server130via the mobile device150. Encryption may be performed by a security unit755(FIG.20) with security technology (e.g., encryption and decryption means) that may be associated with the processing unit750and/or the memory760. Significantly, the AuthRequest is a request for authorization of funds, not a request for authorization of a transaction. The purpose of the funds is irrelevant to the server130.

Authorization Grant Token (“AuthGrant”): This is a “message” (also referred to as a communication or transmissions) encrypted by the security unit955(FIG.22) with security technology (e.g., encryption and decryption means) of the server130with the unique private key corresponding to the adapter module100. The secured authorization grant (e.g., the encrypted authorization grant) is passed from the server130to the adapter module100via the mobile device150in the form of a message. The mobile device150, however, is not able to decrypt and/or read the message. The authorization grant is in response to the authorization request. The amount of the funds granted by the AuthGrant may be determined by factors including, but not limited to, the amount of funds available (or, if funds are not available, a mini-loan could be granted), a pre-authorized amount (e.g., set by the server, set by the user during set-up, set by the funding source, or a standard amount), limited by time (e.g., only a certain amount per hour, or a predetermined amount at specific times of the day), limited to the maximum amount of an item on the machine (or enough for two or three items in the machine), or one or more of these and other factors. Significantly, the AuthGrant makes the funds available, but does not authorize a transaction. The AuthGrant may have an associated expiration period in that it may expire if it is not used in a pre-determined time period. The length of time before the AuthGrant expires may be determined by factors including, but not limited to, the trustworthiness of the user (e.g., the user has a long history with the payment processing system or some known provider (e.g., credit card provider, bank, or credit union), the user has a good credit rating, or the user has a large wallet balance), a pre-authorized time period (e.g., set by the server, set by the user during set-up, set by the funding source, or a standard time period), limited by time (e.g., predetermined time periods at specific times of the day such as longer times during breakfast, lunch, and dinner), limited by the machine or the products or services sold in the machine, limited by the number of other users near the machine (e.g., if it is a crowded machine, the AuthGrant may expire faster), or one or more of these and other factors. The AuthGrant remains valid until it expires or some other event occurs to end its validity (e.g., the user cancels it). This means that under normal circumstances the mobile device150will hold the AuthGrant authorizing use of funds for a pre-determined time period that will allow the user sufficient time to make a purchase. The authorized amount may be considered to be the “wallet balance” that is held in a virtual “wallet.”

Synchronization: Time may be synchronized to the adapter module100from the server130. The server130sends time information with encrypted messages and the adapter module100uses the time encoded in the messages for synchronization.

The mobile-device-to-machine payment processing system and components thereof may have associated hardware, software, and/or firmware (a variation, subset, or hybrid of hardware and/or software). The term “hardware” includes at least one “processing unit,” “processor,” “computer,” “programmable apparatus,” and/or other known or yet to be discovered technology capable of executing instructions or steps (shown as the processing unit750inFIG.20, the processing unit850inFIG.21, and the processing unit950inFIG.22). The term “software” includes at least one “program,” “subprogram,” “series of instructions,” or other known or yet to be discovered hardware instructions or hardware-readable program code. Software may be loaded onto hardware (or firmware) to produce a “machine,” such that the software executes on the hardware to create structures for implementing the functions described herein. Further, the software may be loaded onto the hardware (or firmware) so as to direct the mobile-device-to-machine payment processing system (and components thereof) to function in a particular manner described herein or to perform a series of operational steps as described herein. “Hardware” such as the adapter module100, the mobile device150, and the payment accepting unit120may have software (e.g., programs and apps) loaded thereon. The phrase “loaded onto the hardware” also includes being loaded into memory (shown as the memory760inFIG.20, the memory860inFIG.21, and the memory960inFIG.22) associated with or accessible by the hardware. The term “memory” is defined to include any type of hardware (or other technology)-readable media (also referred to as computer-readable storage medium) including, but not limited to, attached storage media (e.g., hard disk drives, network disk drives, servers), internal storage media (e.g., RAM, ROM, EPROM, FLASH-EPROM, or any other memory chip or cartridge), removable storage media (e.g., CDs, DVDs, flash drives, memory cards, floppy disks, flexible disks), firmware, and/or other known or yet to be discovered storage media. Depending on its purpose, the memory may be transitory and/or non-transitory. Appropriate “messages,” “communications,” “signals,” and/or “transmissions” (that includes various types of information and/or instructions including, but not limited to, data, commands, bits, symbols, voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, and/or any combination thereof) over appropriate “communication paths,” “transmission paths,” and other means for signal transmission including any type of connection between two elements on the payment processing system (e.g., the adapter module100, the mobile device150, the payment accepting unit120, hardware systems and subsystems, and memory) would be used as appropriate to facilitate controls and communications.

It should be noted that the terms “programs” and “subprograms” are defined as a series of instructions that may be implemented as software (i.e. computer program instructions or computer-readable program code) that may be loaded onto a computer to produce a “machine,” such that the instructions that execute on the computer create structures for implementing the functions described herein or shown in the figures. Further, these programs and subprograms may be loaded onto a computer so that they can direct the computer to function in a particular manner, such that the instructions produce an article of manufacture including instruction structures that implement the function specified in the flow chart block or blocks. The programs and subprograms may also be loaded onto a computer to cause a series of operational steps to be performed on or by the computer to produce a computer implemented process such that the instructions that execute on the computer provide steps for implementing the functions specified in the flow chart block or blocks. The phrase “loaded onto a computer” also includes being loaded into the memory of the computer or a memory associated with or accessible by the computer. Separate, albeit interacting, programs and subprograms may be associated with the adapter modules100, the server130, and the mobile device150(including the mobile application140) and these programs and subprograms may be divided into smaller subprograms to perform specific functions.

The terms “messages,” “communications,” “signals,” and/or “transmissions” include various types of information and/or instructions including, but not limited to, data, commands, bits, symbols, voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, and/or any combination thereof. Appropriate technology may be used to implement the “communications,” “signals,” and/or “transmissions” including, for example, transmitters, receivers, and transceivers. “Communications,” “signals,” and/or “transmissions” described herein would use appropriate technology for their intended purpose. For example, hard-wired communications (e.g., wired serial communications) would use technology appropriate for hard-wired communications, short-range communications (e.g., Bluetooth) would use technology appropriate for close communications, and long-range communications (e.g., GSM, CDMA, Wi-Fi, or the like) would use technology appropriate for remote communications over a distance. Appropriate security (e.g., SSL or TLS) for each type of communication is included herein. The security units755and955include technology for securing messages. The security technology may be, for example, encryption/decryption technology (e.g., software or hardware). Although encryption/decryption is discussed primarily as being performed using a unique private key, alternative strategies include, but are not limited to encryption/decryption performed using public/private keys (i.e., asymmetric cryptography), or other encryption/decryption strategies known or yet to be discovered. Appropriate input mechanisms and/or output mechanisms, even if not specifically described, are considered to be part of the technology described herein. The communications unit770(shown inFIG.20) of the adapter module100is shown as including appropriate input and output mechanisms772,774that may be implemented in association (e.g., directly or indirectly in functional communication) with male and female adapters720,730of the adapter module100. The communications unit870(shown inFIG.21) of the mobile device150includes mechanisms for both long-range communications (shown as the long-range communication capability872such as cellular and/or Wi-Fi mechanisms) for communicating with the server130and short-range communications (shown as the short-range communication capability876such as Bluetooth mechanisms) for communicating with the adapter module100.

When used in relation to “communications,” “signals,” and/or “transmissions,” the terms “provide” and “providing” (and variations thereof) are meant to include standard means of provision including “transmit” and “transmitting,” but can also be used for non-traditional provisions as long as the “communications,” “signals,” and/or “transmissions” are “received” (that can also mean obtained). The terms “transmit” and “transmitting” (and variations thereof) are meant to include standard means of transmission, but can also be used for non-traditional transmissions as long as the “communications,” “signals,” and/or “transmissions” are “sent.” The terms “receive” and “receiving” (and variations thereof) are meant to include standard means of reception, but can also be used for non-traditional methods of obtaining as long as the “communications,” “signals,” and/or “transmissions” are “obtained.”

The term “associated” is defined to mean integral or original, retrofitted, attached, connected (including functionally connected), positioned near, and/or accessible by. For example, if the user interface (e.g., a traditional display122(FIG.19), a touch screen display124(FIG.19), a key pad126(FIG.19), buttons126(FIG.19, shown as part of the key pad126), a keyboard (not shown), and/or other input or output mechanism) is associated with a payment accepting unit120, the user interface may be original to the payment accepting unit120, retrofitted into the payment accepting unit120, attached to the payment accepting unit120, and/or a nearby the payment accepting unit120. Similarly, adapter modules100may be associated with payment accepting units120in that the adapter modules100may be original to the payment accepting unit120, retrofitted into the payment accepting unit120, attached to the payment accepting unit120, and/or a nearby the payment accepting unit120.

System Overview

FIGS.5,6, and7together show major components of the mobile-device-to-machine payment system and the interactions there-between.

As shown, the adapter module100functionally connected bi-directionally to the payment accepting unit120via a wired serial connection such that no security is necessary. The adapter module100is also functionally connected bi-directionally to the mobile device150(and its installed mobile application140) via short-range communication technology (e.g., a Bluetooth connection). Because the mobile device150is not a “trusted” link (e.g., it could be hacked by a user), only secured communications (transmissions) are passed between the adapter module100and the mobile device150. This keeps communications secured and safe from hacking. The mobile device150(and its installed mobile application140) is also functionally connected bi-directionally to a system management server130and/or a funding source server160via long-range communication technology (e.g., Wi-Fi or Cellular connection) that preferably has appropriate security (e.g., SSL security). Security between the mobile device150and the system management server130has the advantage of protecting communications from the mobile device150to the system management server130that may include sensitive data and may not be encrypted. The system management server130and the funding source server160may be connected via a wired Internet connection with SSL security. The system management server130may be connected via a wired Internet connection with SSL security to an operators' server170. Although not necessary to implement a purchase transaction, for other purposes (e.g., inventory), the operators' server170may be connected to the payment accepting unit120using a handheld computer sync or a cellular connection.

Also, a unique private key may be used to securely transmit encrypted messages between the adapter module100and the system management server130(although the encrypted transmissions would most likely be routed through the mobile device150). The server130stores a private key for each adapter module100, and this key is only known to the adapter module100and the server130. No intermediary is privy to this key (especially not the mobile device150). When the adapter module100and the server130communicate messages (e.g., AuthRequest and AuthGrant), the security unit755of the adapter module100encrypts the message with its private key and passes the message to the mobile device150. The mobile device150(which preferably cannot decrypt the message) passes the encrypted message to the server130. The server130is able to decrypt the message using the security unit955of the adapter module100and the unique private key. The security unit955of the server130uses this same unique private key to encrypt messages to the adapter module100and sends the message to the mobile device150to relay to the adapter module100that is able to decrypt the message using the security unit755of the adapter module100and the unique private key.

FIG.7shows specific communications and messaging with a vending sequence (the numbers to the left of the communications and messaging) between the adapter module100, the mobile device150, and the system management server130. These communications are discussed in more detail in the discussion pertaining to the schematic flow diagrams (FIGS.8A-8G) and the flow charts (FIGS.9A-9E).

It should be noted thatFIGS.5,6, and7are examples, and are meant to help in the understanding of the mobile-device-to-machine payment system. For example, the shown long-range communications technology may be replaced with alternative long-range communications technology known or yet to be discovered, the shown short-range communication technology may be replaced with alternative short-range communication technology known or yet to be discovered, and the shown security may be replaced with alternative security known or yet to be discovered. The shown connections are meant to be examples, and there may be intermediaries that are not shown. The shown components have been simplified in that, for example, only one mobile device150(or machine120, adapter module100, or server130) is shown where many may be included. Finally, the order of the steps may be changed and some steps may be eliminated.

Adapter Module

FIGS.11-18show views of adapter module100a(referred to generally as adapter module100). Adapter module100is a relatively low cost hardware component that is pre-configured to work with the industry standard multi-drop bus (MDB). On machines without MDB technology, the adapter module100can be configured or designed to work with other serial protocols or activate a switch. In essence the adapter module100simulates establishing payment on payment accepting unit120in much the same manner as other alternative forms of payment (e.g., cash).

The shown adapter modules100are preferably designed to be used as an in-line dongle for in-line insertion within, for example, a MDB of a machine120. The wire used in MDB technology uses male and female connection ends or adapters to allow the attachment of peripherals. In the case of a vending machine, the wire with the connection ends or adapters would be present to allow the attachment of a payment receiving mechanism (e.g., a coin mechanism). The MDB male and female adapters700,710may be separated (as shown inFIGS.17-18). The adapter module100ainFIGS.11and17-18has a male adapter720and a female adapter730. The adapter module100amay be plugged (inserted) in serial (“in-line”) with the wire. For example, the MDB female adapter710may be connected to the male adapter720of the adapter module100and the MDB male adapter700may be connected to the female adapter730of the adapter module100. The resulting in-line configuration is shown inFIG.19. It should be noted that the adapter modules100are designed to allow pass-through communications so that if the mobile-device-to-machine payment processing system is not enabled (e.g., for a particular purchase or simply turned off) the MDB functions as though the adapter module100is not there and the machine120can function normally.

Hands-Free Mode

Summarily, if it is available, a hands-free mode, from the user's perspective, would allow the user to approach a favorite payment accepting unit120and notice that the display (e.g., the displays122or124shown inFIG.19) associated with the payment accepting unit120shows funds available (e.g., the wallet balance), he would select the product or service using input mechanisms (e.g., buttons126or a touch screen display124shown inFIG.19) associated with the payment accepting unit120, and he would retrieve his dispensed services or products.

During an initial handshake with the mobile device150(when the user is within range), the adapter module100reports to the mobile device150whether or not hands-free mode is available. If it is available, the installed mobile application140automatically connects to the payment accepting unit120without the user having to interact with the mobile device150. The user observes that funds are available on the display122,124of the payment accepting unit120and completes the purchase transaction as if cash was inserted in the machine120by inputting his selection on the payment accepting unit120. The payment accepting unit120dispenses the product or service. After the selection is made, the change is returned to the mobile device150.

Whether hands-free payment is available is determined by factors including, but not limited to whether if other mobile devices150are in range, if other adapter modules100are in range, if there are any alerts, if the payment trigger threshold is having wide variances and so deemed unstable, or if the payment accepting unit operator (e.g., a vending machine operator) has opted to disable hands-free mode for the payment accepting unit120. In the latter instance, operators can disable via a maintenance mobile device150, as well as through the operators' server170and/or the system management server130.

FIG.3is a table that shows considerations, conditions, or factors that may be used to determine whether the hands-free pay feature is available. Starting at the “Favorite?” column, this indicates whether the payment accepting unit120is a favorite machine. Preferably the hands-free pay feature is only available for use with “favorite” payment accepting units120(e.g., a vending machine at work or school). The “Alert” column has to do with whether there is some reason (e.g., there are too many users in range) that the hands-free pay feature should not work and, if there is such a reason, the user will be notified (alerted) and may be able to use the manual mode to resolve the alert and/or complete the transaction.FIG.3shows situations in which a user is or is not able to make hands-free purchases from a machine120using a mobile application140on his mobile device150. It should be noted that the shown interface is an example. For example, some of the features could be automated or pre-selected. (It should be noted that the left hand column, the “Tab” column, relates to whether the selected tab on the mobile application140is “all” or “favorite.”FIGS.10A-10Dall show these tabs. Unlike the other columns inFIG.3, this column has more to do with the functionality and view of the application140than specifically with the hands-free feature. The tabs would allow a user to select whether he wanted to be alerted when he was in range of all payment accepting units120or just “favorite” payment accepting units120and the application140would show the appropriate view.)

Balance Display: An optional feature of the mobile-device-to-machine payment system that is particularly helpful in the hands-free mode (although it may be available in the manual mode and/or in a multiple-vend scenarios) is when the user's mobile device150sends “credit” to the payment accepting unit120(either via hands-free payment or through a manual swipe), the wallet balance is sent to the payment accepting unit120that is then displayed to the user on a display122,124of the machine120. This is particularly beneficial during hands-free mode when the user does not retrieve the mobile device150and, therefore, may not know the balance. Also, in a multiple-vend scenario the user would not have to calculate a remaining balance.

An example of a hands-free, multiple-vend scenario where a balance is displayed by the payment accepting unit120, follows: The user has $5.00 in his/her virtual wallet as that is the amount that has been authorized (the AuthGrant being stored on the mobile device150). The user walks up to the payment accepting unit120and $5.00 is displayed on the display122,124of the payment accepting unit120since hands-free mode was enabled and credit was sent (e.g., via the short-range communication capability) to the payment accepting unit120. The user makes a selection of $1.50 by interacting (e.g., pressing buttons) with the machine120. The item (product or service) is dispensed and the “change” is “returned” (e.g., via the short-range communication capability) to the virtual wallet. But since the user is still standing in the payment zone102, the remaining wallet balance of $3.50 is sent to the payment accepting unit120and displayed so that the user can now see that he/she has a $3.50 balance. (It should be noted that the authorized funds may remain on the machine120and not be transferred back to the mobile device150between transactions.) The user decides to purchase a $1.50 item, and the transaction is completed as usual (e.g., by interacting with the machine120). Now the user is still standing in the payment zone102and he/she sees the wallet balance of $2.00 on the display122,124of the payment accepting unit120. The user decides that he/she does not wish to purchase anything else and simply walks away. As he/she walks out of the payment zone102, the credit is cleared from the machine120, but he/she is left with the knowledge that his wallet balance is $2.00 even though he/she never touched the mobile device150. Communications between the payment accepting unit120and the adapter module100(via the mobile device150) handle the accounting incidental to the transaction. The remaining balance ($2.00) is technically stored on the server130, and may be reflected on the application140on the mobile device150.

Multiple Distinct Zones

As shown inFIGS.1-2, the functions performed by the adapter module100can be divided into distinct zones: a first “communication zone” (e.g., “Bluetooth range”106), a second “authorization zone”104, and a third “payment zone”102. The payment zone102is smaller than or equal to (overlapping completely) the authorization zone104. Put another way, the payment zone102is within or coextensive with the authorization zone104. The payment zone102is a subset of the authorization zone104with a ratio of the payment zone102to the authorization zone104ranging from 0.01:1 to 1:1. It is not necessarily a fixed ratio and can vary between different payment accepting units120, different mobile devices150, different users, and over time. While the zones102,104,106are depicted as having a uniform shape, the zones may not necessarily be uniform (or constant over time) in that the shape can vary. For example, the shape of the Bluetooth range106may vary depending on environmental conditions such as obstacles in the room and payment accepting unit120door/wall materials.

Bluetooth Range106(sometimes also herein called the “communication zone”): The outermost range is the Bluetooth range106(shown inFIGS.1-2). This is the area in which the adapter module100is able to broadcast its presence. In most situations, the Bluetooth range106is a passive range in that no actual data is exchanged between the mobile device150and the adapter module100. While in the Bluetooth range106, the mobile device150monitors the RSSI (Received Signal Strength Indicator).

Authorization Zone104: The middle region is the authorization zone104(shown inFIGS.1-2). This is a computed area based on the RSSI. As mentioned, the mobile device150monitors the RSSI while it is in the Bluetooth range106. When the RSSI reaches a certain predetermined threshold based on In-Range Heuristics, the mobile device150can be considered to be in the authorization zone104. In the authorization zone104the mobile device150establishes a connection to the adapter module100(e.g., a Bluetooth connection (FIG.5) with SSL protection (FIG.6)) and informs the adapter module100of its presence. After a successful handshake with the adapter module100, the mobile device150registers the adapter module100and the adapter module100requests an authorization to the server130via the mobile devices' network connection (e.g., a Wi-Fi or cellular connection (FIG.5) with SSL protection (FIG.6)). It is important to note the mobile device150and the adapter module100have a non-exclusive relationship at this point. The adapter module100may collect registrations for all mobile devices150that are within the authorization zone104.

An authorization occurs in preparation for when the user enters the payment zone102(shown inFIGS.1-2). An authorization expires in a set period of time (for example, five minutes), so if the mobile device150is still in the authorization zone104at the time of expiration, the adapter module100submits for and receives another authorization. This will continue for a set number of times (for example, the limit may be three times to limit cases of numerous authorizations for a mobile device that may remain in the authorization zone104for an extended period of time without completing a transaction). Should authorization fail (for instance if the limit had been reached) prior to the user entering the payment zone102, the adapter module100will request authorization when the mobile device150enters the payment zone102(which adds a few seconds to the experience).

Payment Zone102: As a user enters the payment zone102, the mobile device150establishes exclusive control of the adapter module100. Once established, any other user in the payment zone102is put into a “waiting” status.

In the payment zone102, the payment can be triggered automatically if the payment processing system has and is in hands-free mode. In such instances, the mobile device150is running the application140in background mode and will send credit to the payment accepting unit120without any explicit user interaction. The user completes the transaction on the payment accepting unit120in much the same manner as if cash had been inserted into the payment accepting unit120to establish credit. After the user completes the transaction (that may include one or more purchases), details of the transaction are preferably returned to the mobile device150and server130in separate messages. The message to the server130is preferably encrypted with the adapter module's100private key (FIG.6) to ensure data integrity. As shown inFIG.7, the “private key” coded message (Encrypted VendDetails) is preferably sent via the mobile device150. The message to the mobile device150may be sent solely for the purpose of closing the transaction. The transaction history and balance are updated server-side via the encrypted message sent to the server130.

The other mode of operation is manual mode. In manual mode, the user launches the mobile device150and is able to swipe to send payment to the payment accepting unit120. The user can also swipe back to cancel the payment. Like in hands-free mode, the purchase transaction is completed on the payment accepting unit120in the same manner as if cash were inserted into the payment accepting unit120. The mobile device150is only used to send payment. Selection is made directly on the payment accepting unit120.

Self-Calibrating Zone Threshold: A key, but optional feature, of the payment processing system is a self-calibrating payment zone RSSI threshold. Because RSSI can vary machine to machine, environment to environment, and device to device, having a fixed threshold at which payment is triggered can be problematic. The approach suggested herein is the creation of a self-calibrating threshold. When the user is interacting with the payment accepting unit120(such as when he makes his selection on the payment accepting unit120), the payment accepting unit120notifies the adapter module100and the adapter module100logs the conditions such as RSSI, type of user mobile device150, accelerometer data, and other information. It is at this point that it can be ascertained safely that the user is within arm's-length from the payment accepting unit120(by necessity the user is arm's-length because he is making some physical interaction with the payment accepting unit120). This is the only point in the entire transaction in which it can be certain that the user is within arm's-length from the payment accepting unit120.

FIG.4shows a simplified set of steps involved when users enter the payment zone102. Specifically,FIG.4shows that credit is established200(this may have been done in the authorization zone104, but if not it would be handled in the payment zone102), that the user makes a selection using the machine202, that the machine notifies the adapter module of the selection204, that the adapter module (optionally) logs the RSSI206, and that the purchase process(es) continues208. Using the historically logged RSSI data, the adapter module100calculates one of several “average” RSSI using various mathematical models. This “average” could be a traditional average, a moving average, a weighted average, a median, or other similar summary function. The adapter module100could pre-process the historical data before running the function, such as to eliminate top and bottom data points, suspect data points, etc.

Optionally, during the handshake between the mobile device150and the adapter module100, the information transmitted to the adapter module100may include, for example, the model of the mobile device150. Using the received information pertaining to the mobile device models, the adapter module100can create multiple payment thresholds, one for each mobile device model. This allows for variances that may be inherent in different types of Bluetooth radios. An alternative to this method is for the adapter module100to broadcast a baseline payment zone threshold, and the mobile device150can use an offset from this baseline based on its specific model type. The payment zone thresholds (or baseline offsets) can be unique to specific types of mobile devices (e.g., by manufacturer, operating system, or component parts), models of mobile devices, or individual mobile devices (unique to each user).

In a typical scenario in which the payment zone threshold has been calibrated, the adapter module100advertises its presence along with the threshold at which it considers any mobile device150to be in the authorization zone104. This is a one-way communication from adapter module100to mobile device150. Once the mobile device150enters the authorization zone104, there is a handshake that is established between the adapter module100and the mobile device150. During this handshake, the mobile device150can share its model information with the adapter module100, and the adapter module100can return the payment zone102threshold for that specific model.

Optionally, in addition to calibrating the payment zone threshold, the adapter module100can apply the self-calibrating model to the authorization zone104to calibrate the authorization zone threshold. As with the payment zone thresholds, the authorization zone thresholds can be unique to specific types of mobile devices, models of mobile devices, or individual mobile devices. In this scenario, the adapter module100would broadcast multiple thresholds by device type and the mobile device150would determine which threshold to apply (or alternatively broadcast a baseline and the mobile device150uses an offset based on its device model). Even in this scenario, the authorization zone104is a one-way communication.

Optionally, along with the threshold that is calculated (in the payment and/or the authorization zone(s)), a safety margin can be added to minimize scenarios in which a user is within range, but the mobile-device-to-machine payment processing system does not recognize it because the threshold may not have been reached. For example, if the calculated RSSI for an iPhone™ 5 on machine4567is −68 db, the mobile-device-to-machine payment processing system may add a safety margin of −5 db, and establish the threshold at −73 db. So when a user's phone is communicating with the adapter module100at an RSSI of −73 db or better, the mobile-device-to-machine payment processing system will allow the mobile device150to credit the payment accepting unit120. The safety margin can be set on the server130and downloaded to the adapter module100, or set on the mobile device150, or set on the adapter module100itself.

Optionally, in the payment zone threshold, the mobile device150can use other data to determine when to cancel the exclusive control of the payment accepting unit120, to identify when the user is moving out of the payment zone102. External data could include accelerometer data from the mobile device150. Using that data, the mobile device150can determine whether the user is standing relatively still in front of the payment accepting unit120, or if the user is in motion-effectively walking away from the payment accepting unit120.

Signal Unavailability Adaptation

The mobile-device-to-machine payment processing system described herein uses a mobile device's150short-range communication technology (e.g., Bluetooth mechanisms) (shown as short-range communication capability876inFIG.21) and a mobile device's150long-range communications technology (e.g., cellular and/or Wi-Fi mechanisms) (shown as long-range communication capability872inFIG.21). The short-range communication capability876communicates with the adapter module's100short-range communication technology (e.g., Bluetooth mechanisms) (shown as short-range communication capability776inFIG.20). The long-range communication capability872communicates with the server's130long-range communications technology (e.g., cellular and/or Wi-Fi mechanisms) (shown as long-range communication capability972inFIG.22). The mobile device150(with a mobile application140thereon) acts as a communication bridge between the adapter module100(associated with a payment accepting unit120) and the server130. This process is described herein and works properly if there is cellular or Wi-Fi coverage within the payment zone102.

One option if there is no cellular or Wi-Fi coverage within the payment zone102is to determine whether there is cellular or Wi-Fi coverage within the authorization zone104or the Bluetooth range106. If there is, then the sizes of the zones102,104,106could be adapted and the timing could be adapted. For example, if the mobile devices150detected problems with the cellular or Wi-Fi coverage within the payment zone102, the user could carry his mobile device150into the other zones (or the mobile device150could use short-range communication technology to communicate with other mobile devices150within the authorization zone104or the Bluetooth range106) to determine whether the zones have cellular or Wi-Fi coverage. If they do have coverage, communication between the mobile device150and the server130can be advanced (conducted earlier when the mobile device150is further from the machine120) or delayed (conducted later when the mobile device150is further from the machine120). This can be thought of as changing the size or shapes of the zones102,104,106. The timing would also have to be adjusted so that the authorization of funds (AuthGrant) does not expire before the user has a chance to make a purchase. It also means that balance updates to the server130may happen after the user has moved away from the machine120and has cellular or Wi-Fi coverage again.

Another option if there is no cellular or Wi-Fi coverage within any of the zones102,104,106is for the user to obtain authorization while outside of the zones in a place with cellular or Wi-Fi coverage. This may occur, for example, if a user knows that he will be going to a place with a payment accepting unit120equipped with an adapter module100(perhaps to a favorite payment accepting unit120) that does not have (or rarely has) cellular or Wi-Fi coverage. A user may also use the mobile application140to query payment accepting units120in a given range (e.g., within 50 miles) or at a given location (e.g., at a campground or in a particular remote city) to determine whether there is cellular or Wi-Fi coverage within the zones102,104,106. The user can then obtain pre-authorization from the server130using the mobile application140. Again, the timing would also have to be adjusted so that the authorization of funds (AuthGrant) does not expire before the user has a chance to make a purchase. It also means that balance updates to the server130may happen after the user has moved away from the machine120and has cellular or Wi-Fi coverage again. A mobile-device-to-machine payment system having the ability to implement this option would be able to accept cashless payments without requiring any network connection near the payment accepting unit120. In some implementations, the mobile-device-to-machine payment processing systems described herein is located in a remote location where no signal is available, therefore, can accept cashless payments.

As an example of a situation in which there might be no cellular or Wi-Fi coverage within any of the zones102,104,106of a particular payment accepting unit120, the user (a teenager) may be traveling to a remote location to attend summer camp where there is no cellular or Wi-Fi coverage. The camp may have several payment accepting units120(e.g., a machine that creates a dedicated “hot spot” that requires payment for use, vending machines, or machines for renting equipment such as bikes, kayaks, or basketballs). The camp facility might notify parents that the mobile-device-to-machine payment system is available. The parents, while at home, could obtain authorization for a particular amount (that could be doled out a certain amount per day or limited to type of machine or location) to be authorized and “loaded” into the user's mobile device150and specify that the authorization will not expire for a certain period or until a certain date. Thereafter, while at camp, the user could use the mobile application140on his mobile device150in a manner similar to those discussed elsewhere herein. Short-range communications may be used for communications between the adapter modules100(associated with the machines120) and users' mobile devices150.

One subtle but powerful component of the payment processing system described herein is that it requires a long-range communication capability (e.g., an Internet or cellular network connection) only in the authorization zone104and only for the time period required to send the AuthRequest and receive the AuthGrant. Once a valid AuthGrant is received by the mobile device150, the long-range communication capability (e.g., an Internet or cellular network connection) is not required by either the mobile device150or the adapter module100in the payment zone102as long as the AuthGrant is valid (unexpired). This mechanism allows the system to seamlessly handle authenticated transactions in (temporary) offline mode, with the deferred acknowledgement and transaction messages performing the bookkeeping and cleanup when network connection is regained. The alternatives described above provide a unique way to artificially extend the authorization zone to include any location where the mobile device150can communicate with the server130.

Multiple User Resolution

As shown inFIG.2, in one practical scenario, multiple users are in the zones102,104,106. As shown inFIG.2, users1,2, and3are in the payment zone102near the machine120; users5and6are shown as positioned between the authorization zone104and the Bluetooth range106; users4and7are in the Bluetooth range106, user10is positioned on the edge of the Bluetooth range106; and users8and9are positioned outside of Bluetooth range106. In some implementations, the mobile-device-to-machine payment processing system manages and resolves issues pertaining to multiple users.

Users4and7are within the Bluetooth range106and the user10is either entering or leaving the Bluetooth range106. Within the Bluetooth range106the users' mobile devices150are able to see the adapter module's100advertisement. In this zone, the mobile device150preferably does not initiate a connection. The adapter module100is preferably unaware of the users in the Bluetooth range106. All the adapter module100is doing is advertising its presence to any multitude of users that may be in Bluetooth range106.

The adapter module100begins to log users as the users (and their respective mobile devices150) enter the authorization zone104(shown inFIG.2as users5and6). At this point, there is a non-exclusive connection initiated by the mobile device150to the adapter module100. It does a handshake (e.g., to exchange information needed to obtain authorization and, optionally, to log information needed for a self-calibrating authorization zone threshold) and the mobile device150contacts the server130for an authorization (e.g., sending an AuthRequest and receiving an AuthGrant). The adapter module100registers all mobile devices150that have requested and received AuthGrants. The adapter module100continues communicating with any other mobile device150that enters the authorization zone104. After initial contact, the adapter module100may provide the mobile device150with a deferral delay of when to check back in with the adapter module100allowing opportunity for other mobile devices150to communicate with the adapter module100.

If there is only one user in the payment zone102, a purchase transaction may be performed. If there are multiple users in the payment zone102, the mobile-device-to-machine payment system must handle the situation.

One optional solution for handling the situation of the multiple users in the payment zone102is queuing users in the payment zone102. Once any mobile device150enters the payment zone102, it establishes exclusivity to a particular mobile device150(e.g., in a first-come-first-serve manner). Technically, however, the adapter module100is not establishing an exclusive connection to the mobile device150. The adapter module100can still perform a round-robin poll and communicate with and advertise to other mobile devices150. Instead, the adapter module100establishes a queue prioritized by RSSI and time (e.g., who was first and whether the authorization has expired) and it notifies (e.g., alerts) other mobile devices150to wait. The earliest valid (unexpired) authorization takes precedence when there is any tie in the RSSI. Otherwise, for example, the strongest average RSSI takes priority. Preferably the queue is not a static measure of the RSSI but an averaged measure over the period of time in the queue. This compensates for a scenario in which a user may be walking around in the queue and then shows up at the payment accepting unit120just as the previous user is finishing. If another user was also in the payment zone102and stood there the entire time, but may have newer authorization, he could win out.

Anytime that the adapter module100cannot determine exactly which user is in the payment zone102in front of the payment accepting unit120, the adapter module100will disable hands-free payment. The mobile device150will send an alert to the user and he can use swipe to pay (manual mode). All users in payment zone102will show “Connected” and the first to swipe payment to the payment accepting unit120then locks out other users.

Multiple Module Resolution

In the scenario where there are multiple modules present, determining which payment accepting unit120a user is in front of can be a challenge. In some implementations, the mobile-device-to-machine payment processing system described herein allows adapter modules100to communicate to other adapter modules100in range via Bluetooth. Each user receives authorization grants for specific payment accepting units120. This means if there are multiple adapter modules100within the same authorization zone104, there will be multiple authorization grants for the user. When the user enters the payment zone102, it can be difficult to differentiate which payment accepting unit120the user is in front of if the payment zones102overlap.

To solve this problem, when the user enters the payment zone102, the adapter modules100communicate with each other to determine the RSSI for the particular user (based on the signal from his mobile device150) to triangulate which adapter module100(and the associated payment accepting unit120) is closer to the user. Optionally, the inter-module communications can restrict the user to establishing an exclusive connection with only one payment accepting unit120.

Optionally, when the user connects to a payment accepting unit120, the mobile device150can send a communication to the payment accepting unit120for momentary display to the user on the display122,124of the payment accepting unit120. For example, the mobile device150can send a communication (e.g., “connected” or “Fred's Mobile Device Connected”) to the payment accepting unit's display122,124for a predetermined period of time (e.g., 1-3 seconds) so when the user is in payment zone102, it is clear which payment accepting unit120the user is connected to prior to making a purchase (either in hands-free or manual mode).

In addition, when the user is in manual mode, the mobile device150can display (e.g., on the touch screen152as shown inFIGS.10A-10D) a visual indication of the payment accepting unit120(e.g., a picture and/or a payment accepting unit ID of the payment accepting unit120) for visual confirmation. If the user is in manual mode, the user can manually change the payment accepting unit120.

Descriptive Scenario

FIG.7,FIGS.8A-8G, and9A-9E(as well as other figures) can be used to understand a detailed scenario of the mobile-device-to-machine payment processing system described herein. A flow of communications and steps are loosely described below with reference to these (and other figures). It should be noted that alternative scenarios could include, for example, a modified order of the steps performed.

Prior to vending transactions, a user downloads a mobile application140onto his mobile device150, creates an account, and configures a funding source via, for example, a funding source server160. A funding source may be, for example, a debit card, a credit card, campus cards, rewards points, bank accounts, payment services (e.g., PayPal™) or other payment option or combination of payment options known or yet to be discovered. The funding sources may be traditional and/or nontraditional payment sources that are integrated into the ecosystem described herein and then used indirectly as a source of funds. Funds from the funding source are preferably held on the server130such that when an AuthRequest is received by the server130, the server130can send an AuthGrant authorizing funds for a purchase.

The user can specify one or more “favorite” adapter module(s)100(that has a one-to-one relationship to the payment accepting unit120) that he may visit regularly, such as a vending machine at school or work. Favorite adapter modules100appear on a pre-filtered list and allow for additional rich features such as hands-free payment.

The payment accepting unit120may be equipped with an adapter module100that is constantly advertising its availability via Bluetooth (or other “signals,” “communications,” and/or “transmissions”). This ongoing advertising and scanning for adapter modules is shown inFIG.8A. As shown, the mobile device150is continuously scanning for any adapter module100within Bluetooth (or other “signal,” “communication,” and/or “transmission”) range. When the user is within range of that adapter module100, the mobile device150tracks and monitors the signal strength until a predetermined “authorization zone” threshold is achieved.

FIGS.8B and9Agenerally show that when the authorization zone threshold is reached, the mobile device150enters the authorization zone (block302) and registers the adapter module100. The mobile device150connects to the server130(block304). The application140on the mobile device150creates a request for authorization (AuthRequest) and passes the AuthRequest to the server130using appropriate communication technology (e.g., GSM, CDMA, Wi-Fi, or the like) (block306). The server130responds with an authorization grant (AuthGrant) encrypted with the specific adapter module's private key (block306). This authorization token may minimally include the User identifier (ID), Apparatus ID (for the adapter module100), authorization amount, and expiration time. The mobile device150receives the AuthGrant from the server130, and retains it until the mobile device150is ready to issue payment to an adapter module100. The mobile device150collects all pending AuthGrants that may be one or more depending on how many adapter modules100are in-range. Unused AuthGrants that expire are purged from the mobile device150and the server130. It is important to note that the mobile device150is unable to read the AuthGrant because it is encrypted with the adapter module's unique private key that is only known to server130and adapter module100. This provides a preferred key element of security in the system as the adapter module100only trusts AuthGrants that are issued by the server130, and the AuthGrants cannot be read or modified by the mobile device150or any other party in between the server and the adapter module100. Additional mobile devices150may enter the authorization zone104(block308).

As the user approaches a specific adapter module100, the user enters the payment zone102and an event threshold is triggered based on heuristics performed by the mobile device150. Blocks310and312show the loop steps of waiting for a mobile device150from the authorization zone104to enter the payment zone102. If the user leaves the authorization zone104without entering the payment zone102, the adapter module100returns to advertising its presence (block300).

FIGS.8C and9Bgenerally show the user entering the payment zone. The mobile device150verifies that it has an unexpired and valid AuthGrant. If the AuthGrant is not good, it may be requested again, repeating the Authorization Request process (block315). If the AuthGrant is good, the mobile device150sends the valid AuthGrant (including the wallet balance (block322)) to the adapter module100to initiate a transaction. The mobile device150may issue the AuthGrant automatically without specific user interaction if the hands-free mode is supported (and the device is a favorite (block318), there is only one device in the payment zone102(block318), and (optionally) there is only one user in the authorization zone104(block320). If any of these factors are not present, the mobile device150will prompt and/or wait for the user to begin the transaction manually (block324).

FIGS.8D,9C, and9Dgenerally show the transaction process. As shown inFIG.9C, the adapter module100runs through a series of questions to determine if there are any issues that would prevent vending including: has the user canceled in-app? (block326), has the user walked away? (block328), is the coin return pressed? (block330), has more than a predetermined period of time elapsed? (block332). If the answer to any of these questions is “yes,” the transaction does not proceed. If the answers to all of these questions is “no,” the user makes a selection (block334) on the payment accepting unit120in the same or similar manner as compared to if cash or credit were presented to the payment accepting unit120. If the machine120is able to vend (block336), it attempts to release the product. If the vend fails (block338) it is reported by the machine (block340) and a credit is returned to the virtual wallet (block342). If the vend is successful (block338) it is reported by the machine (block344). Put another way, after the transaction is complete, the adapter module100returns to the mobile device150the details of the transaction as well as an encrypted packet containing the vend details to be sent to the server130via the mobile device150. Optionally, the adapter module100can pass additional information not directly related to the transaction such as payment accepting unit health, sales data, error codes, etc.

FIGS.8D and9Egenerally show the multi-vend function. If the machine has enabled multi-vend capabilities (block350) and the multi-vend limit has not been reached, the process returns to the question of whether the user is in the payment zone (block310ofFIG.9A). If the machine does not have enabled multi-vend capabilities (block350) or the multi-vend limit has been reached, the wallet is decremented by the vend amount(s) and “change” is returned to the virtual wallet (block354) and the process ends (block356).

FIG.8Eis a schematic flow diagram of an example login process.FIG.8Fis a schematic flow diagram of an example boot-up process.FIG.8Gis a schematic flow diagram of an example account check/update process.

Several of the figures are flow charts (e.g.,FIGS.9A-9E) illustrating methods and systems. It will be understood that each block of these flow charts, components of all or some of the blocks of these flow charts, and/or combinations of blocks in these flow charts, may be implemented by software (e.g., coding, software, computer program instructions, software programs, subprograms, or other series of computer-executable or processor-executable instructions), by hardware (e.g., processors, memory), by firmware, and/or a combination of these forms. As an example, in the case of software, computer program instructions (computer-readable program code) may be loaded onto a computer to produce a machine, such that the instructions that execute on the computer create structures for implementing the functions specified in the flow chart block or blocks. These computer program instructions may also be stored in a memory that can direct a computer to function in a particular manner, such that the instructions stored in the memory produce an article of manufacture including instruction structures that implement the function specified in the flow chart block or blocks. The computer program instructions may also be loaded onto a computer to cause a series of operational steps to be performed on or by the computer to produce a computer implemented process such that the instructions that execute on the computer provide steps for implementing the functions specified in the flow chart block or blocks. Accordingly, blocks of the flow charts support combinations of steps, structures, and/or modules for performing the specified functions. It will also be understood that each block of the flow charts, and combinations of blocks in the flow charts, may be divided and/or joined with other blocks of the flow charts without affecting the scope of the invention. This may result, for example, in computer-readable program code being stored in whole on a single memory, or various components of computer-readable program code being stored on more than one memory.

Additional Implementations

FIG.23illustrates a schematic flow diagram of a process1000of authenticating a user to perform a transaction in the payment processing system in accordance with some implementations. In some implementations, the payment processing system includes one or more payment modules100(e.g., each associated with a respective payment accepting unit120such an automatic retailing machine for dispensing goods and/or services), one or more mobile devices150(e.g., each executing the application140for the payment processing system either as a foreground or background process), and the server130. The server130manages the payment processing system and, in some cases, is associated with an entity that supplies, operates, and/or manufactures the one or more payment modules100. For brevity, the process1000will be described with respect to a respective payment module100and a respective mobile device150in the payment processing system.

The payment module100broadcasts (1002), via a short-range communication capability (e.g., BLE), a packet of information (sometimes also herein called “advertised information”). The packet of information at least includes an authorization code and an identifier associated with the payment module100(module ID). In some implementations, the packet of information further includes a firmware version of the payment module100and one or more status flags corresponding to one or more states of the payment module100and/or the payment accepting unit120. The information included in the packet broadcast by the payment module100is further discussed below with reference toFIG.24A.

In some implementations, the payment module100sends out a unique authorization code every X seconds (e.g., 100 ms, 200 ms, 500 ms, etc.). In some implementations, the unique authorization codes are randomly or pseudo-randomly generated numbers. In some implementations, the payment module100stores broadcasted authorization codes until a received authorization grant token matches one of the stored authorization codes. In some implementations, the payment module100stores broadcasted authorization codes for a predetermined amount of time (e.g., Y minutes) after which time an authorization code expires and is deleted. In some implementations, the authorization code is encrypted with a shared secret key known by the server130but unique to the payment module100. In some implementations, the payment module100initializes a random number and then the authorization codes are sequential counts from this random number. In such implementations, the payment module100stores the earliest valid (unexpired) counter without a need to store every valid authorization code. In some implementations, the authentication code included in the broadcast packet of information is a hash value of the randomly or pseudo-randomly generated number or the sequential number.

The mobile device150receives the broadcasted packet of information, and the mobile device150sends (1004), via a long-range communication capability (e.g., GSM, CDMA, Wi-Fi, or the like), an authorization request to the server130. For example, an application140that is associated with the payment processing system is executing as a foreground or background process on the mobile device150. In this example, the application140receives the broadcasted packet of information when the mobile device150is within the communication zone of the payment module100(i.e., BLE range) and either automatically sends the authorization request to the server130or sends the authorization request to the server130when the mobile device150is within the authorization zone of the payment module100. In some implementations, the broadcasted packet of information includes a baseline authorization zone threshold (i.e., an authorization zone criterion) indicating a baseline RSSI that the mobile device150(or the application140) is required to observe before being within the authorization zone of the payment module100. In some implementations, the mobile device150(or the application140) offsets the baseline authorization zone threshold based on the strength and/or reception of the short-range communication capability (e.g., BLE radio/transceiver) of the mobile device150. In some implementations, the authorization request at least includes the authorization code which was included in the broadcasted packet of information, an identifier associated with the user of the mobile device150or the user account under which the user of the mobile device150is logged into the application140(user ID), and the identifier associated with the payment module100(module ID). In some implementations, the authentication code included in authorization request is the hash value in cleartext. The authorization request is further discussed below with reference toFIG.24B.

After receiving the authorization request, the server130processes (1006) the authorization request. In some implementations, the server130decrypts the authorization code included in the authorization request with the shared secret key corresponding to the payment module100. In some implementations, the server130determines whether the user associated with the user ID in the authorization request has sufficient funds in his/her account for the payment processing system to perform a transaction at the machine120that is associated with the payment module100corresponding to the module ID in the authorization request.

The server130sends (1008), via a long-range communication capability (e.g., GSM, CDMA, Wi-Fi, or the like), an authorization grant token to the mobile device150. In some implementations, the server130does not send the authorization grant token if the authorization code in the authorization request cannot be decrypted with the shared secret key corresponding to the payment module100(e.g., the authorization code is corrupted or hacked). In some implementations, the server130does not send the authorization grant token if the user associated with the user ID in the authorization request does not have sufficient funds in his/her account. In some implementations, in addition to the authorization grant token, the server130sends a message directly to the mobile device150which is not encrypted with the shared secret key corresponding to the payment module100. After receiving the message, the mobile device150displays an appropriate message to the user such as insufficient balance or declined authorization. In some implementations, the server130sends an authorization grant token for an amount equal to zero; in which case, the payment module100interprets this as a declined or failed authorization which can result for any number of reasons including, but not limited to, insufficient balance or credit.

The mobile device150receives the authorization grant token, and, subsequently, the mobile device150detects (1010) a trigger condition. In some implementations, the mobile device150(or the application140) detects the trigger condition via the hand-free mode (e.g., upon entrance into the payment zone of the payment module100) or manual mode (e.g., interacting with the user interface of the application140to initiate a transaction with the payment accepting unit associated with the payment module100).

In some implementations, unused authorization grants (e.g., if there was no trigger condition or it expired) are canceled by the mobile device150by sending a cancellation message to the server130corresponding to the unused authorization grant. In some implementations, the server130denies or limits the number of authorization grants sent to the mobile device150until it has received transaction information or cancellation of authorization outstanding authorization grants sent to the mobile device150.

In response to detecting the trigger condition, the mobile device150sends (1012), via a short-range communication capability (e.g., BLE), the authorization grant token to the payment module100. Subsequently, the machine120displays credit to the user (e.g., via one of the displays122or124shown inFIG.19) and the user interacts with the input mechanisms of the machine120(e.g., via the buttons126or a touch screen display124shown inFIG.19) to purchase products and/or services.

FIG.24Aillustrates a block diagram of a packet1100of information broadcast by the payment module100(e.g., in step1002of the process1000inFIG.23) in accordance with some implementations. In some implementations, the packet1100at least includes: module ID1102and authorization code1104. In some implementations, the packet110additional includes: a firmware version1106and one or more status flags1108.

In some implementations, the module ID1102is a unique identifier corresponding to the payment module100(sometimes also herein called the “adapter module100”) that broadcast the packet1100.

In some implementations, the authorization code1104is a hash value in cleartext. In some implementations, the payment module100randomly or pseudo-randomly generates a number or determines a sequential number (See step1002of process1000inFIG.23) and performs a predetermined hash function (e.g., SHA-256) on the number to produce the hash value as the authorization code1104. In some implementations, the authorization code1104is a unique code that is encrypted with a secret encryption key corresponding to the payment module100. The secret encryption key is shared with the server130, which enables the server130to decrypt the authorization code1104and encrypt the authorization grant token but not the mobile device150. In some implementations, the encryption between server130and payment module100is accomplished by two pairs of public/private keys.

In some implementations, the firmware version information1106identifies a current firmware version1112of the payment module100. In some implementations, the firmware version information1106also includes update status information1114indicating one or more packets received by the payment module100to update the firmware or one or more packets needed by the payment module100to update the firmware. In some implementations, the one or more status flags1108indicate a state of the payment module100and/or the payment accepting unit120associated with the payment module100. In some implementations, the one or more status flags1108indicate a state of the payment module100such upload information indicator1116indicating that that the payment module100has information to be uploaded to the server130(e.g., transaction information for one or more interrupted transactions). In some implementations, upload information indicator1116triggers the mobile device150to connect to payment module100immediately (e.g., if it has interrupted transaction information to be uploaded to the server130). In some implementations, the one or more status flags1108indicate a state of the payment accepting unit120including one or more of an error indicator1118(e.g., indicating that a bill and/or coin acceptor of the payment accepting unit120is experiencing a jam, error code, or malfunction), a currency level indicator1120(e.g., indicating that the level of the bill and/or coin acceptor reservoir of the payment accepting unit120is full or empty), and/or inventory level(s) indicator1122(e.g., indicating that one or more products of the payment accepting unit120. In some implementations, the one or more status flags1108are error codes issued by payment accepting unit120over the MDB.

In some implementations, the zone criteria information1110specifies an authorization zone criterion1124(e.g., a baseline authorization zone threshold indicating a baseline RSSI that the mobile device150(or the application140) is required to observe before being within the authorization zone of the payment module100) and/or a payment zone criterion1126(e.g., a baseline payment zone threshold indicating a baseline RSSI that the mobile device150(or the application140) is required to observe before being within the payment zone of the payment module100). In some implementations, the baseline authorization zone threshold and the baseline payment zone threshold are default values determined by the server130or stored as variables by the application140, in which case the authorization zone criterion1124and payment zone criterion1126are offsets to compensate for the strength and/or reception of the short-range communication capability (e.g., BLE radio/transceiver) of the payment module100. Alternatively, zone criteria information1110includes a spread between the baseline authorization zone threshold and the baseline payment zone threshold. Thus, the mobile device150(or the application140) determines the baseline authorization zone threshold and the baseline payment zone threshold based on the spread value and a default value for either the baseline authorization zone threshold or the baseline payment zone threshold. For example, the spread indicates −10 db and the default baseline payment zone threshold is −90 db; thus, the baseline authorization zone threshold is −80 db. Continuing with this example, after determining the baseline authorization zone threshold and the baseline payment zone threshold, the mobile device150(or the application140) may further adjust the authorization zone threshold and/or the payment zone threshold based on the strength and/or reception of its short-range communication capability (i.e., BLE radio/transceiver).

FIG.24Bis a block diagram of an authorization request1130sent by the mobile device150to the server130(e.g., in step1004of the process1000inFIG.23) in accordance with some implementations. In some implementations, the authorization request1130at least includes: a module ID1102, a user ID1134, and an authorization code1104.

In some implementations, the module ID1102is a unique identifier corresponding to the payment module100that broadcast the1100that included the authorization code1104.

In some implementations, the user ID1134is an identifier associated with the user of the mobile device150sending the authorization request1130to the server130. In some implementations, the user ID1134is associated with the user account under which the user of the mobile device150is logged into the application140.

In some implementations, the authorization code1130includes the authorization code1104included in the packet1100of information that was broadcast by the payment module100.

FIG.24Cis a block diagram of an authorization grant token1140sent by the server130to the mobile device150(e.g., in step1008of the process1000inFIG.23) in accordance with some implementations. In some implementations, in accordance with a determination that the authorization code1136included in the authorization request1130from the mobile device150is valid and that the user associated with the mobile device150has sufficient funds in his/her account for the payment processing system, the server130generates the authorization grant token1140. In some implementations, the authorization grant token1140at least includes: a module ID1102, a user ID1134, an authorized amount1146, (optionally) an expiration period offset1148, and (optionally) the authorization code1104.

In some implementations, the module ID1102is a unique identifier corresponding to the payment module100that broadcast the packet1100that included the authorization code1104.

In some implementations, the user ID1134is an identifier associated with the user of the mobile device150that sent the authorization request1130to the server130.

In some implementations, the authorized amount1146indicates a maximum amount for which the user of the mobile device150is authorized for a transaction using the authorization grant token1140. For example, the authorized amount1146is predefined by the user of the mobile device150or by the server130based on a daily limit or based on the user's total account balance or based on a risk profile of the user correspond to the user ID1134.

In some implementations, the expiration period1148offset indicates an offset to the amount of time that the payment module100holds the authorization grant token1140valid for initiation of a transaction with the machine120associated with the payment module100. For example, the expiration period offset1148depends on the history and credit of the user of mobile device150or a period predefined by the user of mobile device150.

In some implementations, the authorization grant token1140further includes the authorization code1104that was included in the authorization request1130. In some implementations, when the authorization code1104is the hash value, the server130encrypts the authorization grant token1140including the hashed value with the shared secret encryption key associated with payment module100. Subsequently, when mobile device150sends the authorization grant token1140to payment module100after detecting a trigger condition, the payment module100decrypts the authorization grant token1140using the secret key known only to server130and payment module100(which authenticates the message and the authorization grant), and then matches the hash value included in the decrypted authorization grant token1140to previously broadcast valid (unexpired) hash values (i.e., auth codes) to determine validity of the (which was known only by payment module100).

FIG.24Dillustrates a block diagram of transaction information1150generated by the payment module100(e.g., in step1254of the process1250inFIG.25B) in accordance with some implementations. In some implementations, the transaction information1150includes: a transaction ID1152for the respective transaction, a module ID1154, a user ID1156, (optionally) the authorization code1158, transaction status information1160, the transaction amount1162, and other information1164.

In some implementations, the transaction ID1152is a unique identifier corresponding to the respective transaction. In some implementations, the transaction ID1152is encoded based on or associated with the time and/or date on which and the location at which the respective transaction took place.

In some implementations, the module ID1154is a unique identifier corresponding to the payment module100that performed the respective transaction.

In some implementations, the user ID1156is an identifier associated with the user of the mobile device150that initiated the respective transaction.

In some implementations, the authorization code1158corresponds to the original authorization code (e.g., auth code1104,FIGS.24A-24C) and/or authorization grant token (e.g., auth grant token1140,FIG.24C) that was used to initiate the respective transaction. In some implementations, the authorization code1156is encrypted with a unique encryption key corresponding to the payment module100.

In some implementations, the transaction status information1160includes an indication whether the respective transaction was completed, not-completed, or aborted. For example, the respective transaction is incomplete if a jam occurred at the payment accepting unit120and the user did not receive the product associated with the respective transaction. For example, if the user walks away from the payment accepting unit120after money was credited for the respective transaction, the respective transaction is aborted. In another example, if respective transaction times out after a predetermined time period because the user failed to select a product at the payment accepting unit120, the respective transaction is aborted. In another example, if the user actuates a bill or coin return mechanism of the payment accepting unit120, the respective transaction is aborted.

In some implementations, the transaction amount1162indicates the amount of the respective transaction or the amount of each of multiple transactions (e.g., in a multi-vend scenario). In some implementations, the transaction amount1162is encrypted with a unique encryption key corresponding to the payment module100.

In some implementations, the other information1164includes other information related to the respective transaction such as the items dispensed by the payment accepting unit120and the type of transaction (e.g., coins, bills, credit card, manual mode, hands-free mode, etc.). In some implementations, the other information1164includes other information related to the payment module100and/or the payment accepting unit120associated with the payment module100. For example, the other information1164includes a verification request to the server130in order to implement new firmware. In another example, the other information1164includes transaction information from one or more previous interrupted transactions. In another example, the other information1164includes transaction information for one or more transactions paid via bills and/or coins. In another example, the other information1164includes inventory information as to one or more products of the payment accepting unit120.

FIG.25Aillustrates a schematic flow diagram of a process1200for providing a representation of a machine event at a mobile device in accordance with some implementations. In some implementations, the payment processing system includes one or more payment modules100(e.g., each associated with a respective payment accepting unit120such an automatic retailing machine for dispensing goods and/or services), one or more mobile devices150(e.g., each executing the application140for the payment processing system either as a foreground or background process), and the server130. The server130manages the payment processing system and, in some cases, supplies, operates, and/or manufactures the one or more payment modules100. For brevity, the process1200will be described with respect to a respective payment module100associated with a respective payment accepting unit120(sometimes also herein called the “machine120”) and a respective mobile device150in the payment processing system.

In some implementations, the process1200occurs after the mobile device150sends the AuthGrant inFIG.8C. In some implementations, the process1200occurs after the mobile device150sends the authorization grant to the payment module100in operation1012of process1000inFIG.23.

The payment module100obtains (1202) an indication corresponding to an event at the machine120. For example, after the process1000inFIG.23, the user of the mobile device150selects a product to purchase from the machine120by interacting with one or more input mechanisms of the machine120(e.g., buttons126or a touch screen display124shown inFIG.19), and the machine120dispenses the selected product. Continuing with this example, after the product is dispensed, the transaction is complete and the payment module100obtains an indication from the machine of the completed transaction. In some implementations, the indication includes the amount of the transaction and (optionally) machine status information associated with the machine120such as inventory information as to one or more products of the payment accepting unit120and/or the like. In some implementations, the indication includes status information indicating that the transaction was aborted (e.g., via actuation of a coin return mechanism at the machine120) or that there was an error with the transaction (e.g., a vending jam or other malfunction with the machine120).

After obtaining the indication corresponding to completion of the first transaction, the payment module100generates (1204) a notification corresponding to the event at the machine120.

The payment module100sends (1206), via a short-range communication capability (e.g., BLE), the notification to the mobile device150. In some embodiments, in addition to the notification corresponding to the event at machine120, the payment module100sends a promotion or advertisement to the mobile device150that is targeted to the user of the mobile device150based on the transaction or the user ID included in the AuthGrant or authorization grant token that initiated the transaction. In some embodiments, in addition to the notification corresponding to the event at machine120, the payment module100sends a pseudo randomly selected promotion or advertisement to the mobile device150that is selected from a set of promotions or advertisements stored by the payment module100. For example, the promotion is a coupon for a free soda following the purchase of ten sodas from the machine120by the user of the mobile device150. For example, the promotion is a random 50% off coupon or free soda coupon. For example, the transaction corresponds to a vended soda and the advertisement corresponds to a new soda from the same company that produces the vended soda.

The mobile device150provides (1208) a representation of the notification. For example, inFIG.26A, the mobile device150displays user interface1302on touch screen152with a message1306that indicates that the first transaction is complete. For example, inFIG.26C, the mobile device150displays user interface1320on touch screen152with a message1322that indicates that the transaction was aborted. For example, inFIG.26D, the mobile device150displays user interface1330on touch screen152with a message1332that indicates that there was an error with the transaction. For example, the mobile device150also displays a representation of the promotion of advertisement on the user interface for the application140.

FIG.25Billustrates a schematic flow diagram of a process1250for processing acknowledgement information in accordance with some implementations. In some implementations, the payment processing system includes one or more payment modules100(e.g., each associated with a respective payment accepting unit120such an automatic retailing machine for dispensing goods and/or services), one or more mobile devices150(e.g., each executing the application140for the payment processing system either as a foreground or background process), and the server130. The server130manages the payment processing system and, in some cases, supplies, operates, and/or manufactures the one or more payment modules100. For brevity, the process1250will be described with respect to a respective payment module100associated with a respective payment accepting unit120(machine120) and a respective mobile device150in the payment processing system.

In some implementations, the process1250occurs after the mobile device150sends the AuthGrant inFIG.8C. In some implementations, the process1250occurs after the mobile device150sends the authorization grant to the payment module100in operation1012of process1000inFIG.23.

The payment module100obtains (1252) an indication corresponding to completion of a first transaction from the machine120. For example, after the process1000inFIG.23, the user of the mobile device150selects a product to purchase from the machine120by interacting with one or more input mechanisms of the machine120(e.g., buttons126or a touch screen display124shown inFIG.19), and the machine120dispenses the selected product. Continuing with this example, after the product is dispensed, the transaction is complete and the payment module100obtains an indication from the machine of the completed transaction. In some implementations, the indication includes the amount of the transaction and (optionally) machine status information associated with the machine120such as inventory information as to one or more products of the payment accepting unit120and/or the like.

After obtaining the indication corresponding to completion of the first transaction, the payment module100generates (1254) a first notification with first transaction information based on the indication, and the payment module100stores the first transaction information. In some implementations, the first transaction information includes a transaction ID for the first transaction, a module ID corresponding to payment module100, a user ID corresponding to the mobile device150, transaction status information indicating that the first transaction is complete, and the transaction amount indicated by the indication. In some implementations, the payment module100retains the authorization code included in the original broadcasted packet and/or the authorization grant token and includes the authorization code in the first transaction information. In some implementations, the authorization code is encrypted with a secret key corresponding to the payment module100, which is shared with the server130but not the mobile device150. In some implementations, the first transaction information further includes other information such as the machine status information included in the first notification or transaction information corresponding to previous interrupted transaction(s). SeeFIG.24Dand the accompanying text for further discussion regarding transaction information1150.

The payment module100sends (1256), via a short-range communication capability (e.g., BLE), the first notification with first transaction information to the mobile device150. In some embodiments, in addition to first transaction information corresponding to completion of the first transaction at machine120, the first notification includes a promotion or advertisement to the mobile device150that is targeted to the user of the mobile device150based on the transaction or the user ID included in the AuthGrant or authorization grant token that initiated the transaction. In some embodiments, in addition to first transaction information corresponding to completion of the first transaction at machine120, the first notification includes a pseudo randomly selected promotion or advertisement to the mobile device150that is selected from a set of promotions or advertisements stored by the payment module100. For example, the promotion is a coupon for a free soda following the purchase of ten sodas from the machine120by the user of the mobile device150. For example, the promotion is a random 50% off coupon or free soda coupon. For example, the transaction corresponds to a vended soda and the advertisement corresponds to a new soda from the same company that produces the vended soda.

The mobile device150provides (1258) a representation of the first notification. For example, inFIG.26A, the mobile device150displays user interface1302on touch screen152with a message1306that indicates that the first transaction is complete. For example, the mobile device150also displays a representation of the promotion of advertisement on the user interface for the application140.

The mobile device150sends (1260), via a long-range communication capability (e.g., GSM, CDMA, Wi-Fi, or the like), the first transaction information to the server130.

The server130processes (1262) the first transaction information. For example, the server130debits the account of the user associated with the user ID in the first transaction information in the amount indicated by the first transaction information.

The server130sends (1264), via a long-range communication capability (e.g., GSM, CDMA, Wi-Fi, or the like), first acknowledgment information to the mobile device150. In some implementations, the first acknowledgment information acknowledges that the server130received the first transaction information. In some implementations, the first acknowledgment information includes the user ID, the module ID, the transaction ID, and (optionally) the authorization grant included in the transaction information (e.g., auth grant1158,FIG.24D).

After receiving the first acknowledgement information, the mobile device150sends (1266), via a short-range communication capability (e.g., BLE), the first acknowledgment information to the payment module100.

After receiving the first acknowledgment information, the payment module100deletes (1268) the stored first transaction information.

Attention is now directed towards implementations of user interfaces and associated processes that may be implemented on the mobile device150with zero or more speakers, zero or more microphones, and a display. For example, the display is a touch screen (sometimes also herein called a “touch screen display”) enabled to receive one or more contacts and display information (e.g., media content, websites and web pages thereof, user interface for the application140, and/or user interfaces for applications).FIGS.26A-26Dillustrate example user interfaces for providing a representation of a machine event at a mobile device in accordance with some implementations.

FIGS.26A-26Dshow user interfaces displayed on mobile device150(e.g., a mobile phone); however, one skilled in the art will appreciate that the user interfaces shown inFIGS.26A-26Dmay be implemented on other similar computing devices. The user interfaces inFIGS.26A-26Dare used to illustrate the processes described herein, including the process described with respect toFIGS.25A-25B and27A-27B.

For example, a user of the mobile device150approaches a machine120(e.g., vending machine78×928 as shown inFIGS.10A-10D) and executes application140on the mobile device150so as to perform an electronic transaction with the machine120. For example, with reference toFIGS.10C-10D, the user of the mobile device150initiates a transaction with the machine120(e.g., vending machine78×928) by performing a swipe gesture at a location corresponding to the representation of the dollar bill (e.g., a substantially vertical swipe gesture from a location corresponding to the representation of the dollar bill to the top edge of the mobile device150).

FIG.26Aillustrates the mobile device150displaying a user interface1302of the application140on touch screen152after the user of the mobile device150initiates and performs a transaction with the machine120. InFIG.26A, the user interface1302includes prepaid balance1304which indicates that $1.00 has been deducted from the prepaid balance after performing a transaction with the machine120as compared to the prepaid balance inFIG.10C-10D(i.e., $9.00 inFIGS.10C-10Dand $8.00 inFIG.26A). InFIG.26A, the user interface1302also includes a message1306indicating that the transaction with the machine120is complete.

FIG.26Billustrates the mobile device150displaying a user interface1310of the application140on touch screen152after the user of the mobile device150initiates a transaction with the machine120and an error with the transaction occurs or the transaction is aborted. InFIG.26B, the user interface1310shows the representation of the dollar bill sliding onto the touch screen152(e.g., in a substantially top to bottom manner). InFIG.26B, the interface1310includes prepaid balance1312which indicates that no money has been deducted from the prepaid balance after performing a transaction with the machine120as compared to the prepaid balance inFIG.10C-10D(i.e., $9.00 inFIGS.10C-10Dand $9.00 inFIG.26B).

FIG.26Cillustrates the mobile device150displaying a user interface1320of the application140on touch screen152after the representation of the dollar bill slides onto the touch screen152inFIG.26Bdue to the transaction being aborted. For example, the user aborts the transaction by actuating a coin return mechanism of the machine120. In another example, the user aborts the transaction by selection an abort affordance on the interface of the application140(not shown). InFIG.26C, the user interface1320includes a message1322indicating that the transaction with the machine120was aborted and that the user's account was not debited for the aborted transaction.

FIG.26Dillustrates the mobile device150displaying a user interface1330of the application140on touch screen152after the representation of the dollar bill slides onto the touch screen152inFIG.26Bdue to the occurrence of an error with the transaction. For example, a malfunction with the machine120(e.g., a vending jam or stuck item) causes the error to occur. InFIG.26D, the user interface1330is associated with the application140executed on the mobile device150. InFIG.26D, the user interface1330includes a message1332indicating that an error occurred during the transaction with the machine120and that the user's account was not debited for the transaction.

FIGS.27A-27Billustrate a flowchart diagram of a method1400of presenting representations of payment accepting unit events in accordance with some implementations. In some implementations, the method1400is performed by a device with one or more processors, memory, one or more output devices, and two or more communication capabilities. For example, in some implementations, the method1400is performed by the mobile device150(FIGS.5and21) or a component thereof (e.g., the application140). In some implementations, the method1400is governed by instructions that are stored in a non-transitory computer readable storage medium (e.g., the memory860,FIG.21) and the instructions are executed by one or more processors (e.g., the processing unit850,FIG.21) of the device. Optional operations are indicated by dashed lines (e.g., boxes with dashed-line borders).

After sending a request to a payment module via a first communication capability transaction to initiate a transaction with a payment accepting unit (e.g., an offline-payment operated machine such as a vending machine or kiosk) associated with the payment module, the mobile device obtains (1402) a notification from the payment module via the first communication capability, where the notification indicates an event at the payment accepting unit associated with the payment module. In some implementations, method1400occurs after the mobile device150sends the AuthGrant inFIG.8C. In some implementations, method1400occurs after the mobile device150sends the authorization grant to the payment module100in operation1012of process1000inFIG.23. Operation1206ofFIG.25A, for example, shows the mobile device150receiving a notification sent by the payment module100(e.g., the adapter module100,FIGS.5and20) sent via the first communication capability (e.g., a short-range communication technology/protocol such as BLE). The notification indicates an event at the payment accepting unit (e.g., the payment accepting unit120,FIGS.5and19) (sometimes also herein called “machine120”) associated with the payment module100.

In some implementations, the first communication capability corresponds (1404) to a short-range communication protocol. As described above, the short-range communication protocols include BLE, NFC, and/or other protocols utilizing non-persistent communication channels.

In response to obtaining the notification, the mobile device provides (1406) a representation of the notification to a user of the mobile device via the one or more output devices of the mobile device. For example, inFIG.26A, the mobile device150displays user interface1302on touch screen152with a message1306that indicates that the first transaction is complete. For example, inFIG.26C, the mobile device150displays user interface1320on touch screen152with a message1322that indicates that the transaction was aborted. For example, inFIG.26D, the mobile device150displays user interface1330on touch screen152with a message1332that indicates that there was an error with the transaction.

In some implementations, the one or more output devices of the mobile device include (1408) at least one of: a display, one or more speakers, one or more LEDs, and a vibration mechanism. For example, the mobile device150includes one or more of a display (e.g., the touch screen152,FIGS.10A-10D), one or more speakers, one or more LEDs, and a vibration mechanism.

In some implementations, the representation of the notification is at least one of (1410): a message displayed on the display of the mobile device; a banner notification displayed on a display of the mobile device; a vibration alert from the vibration mechanism of the mobile device; an aural alert from the one or more speakers of the mobile device; and a visual alert from the one or more LEDs of the mobile device. For example, inFIGS.26B-26D, the representation of the notification includes messages1306,1322, and1332displayed on the touch screen152of the mobile device150. In another example, the representation of the notification is a predefined sequence of vibrations provided by the vibration mechanism of the mobile device150. In another example, the representation of the notification is a predefined sequence of tones provided by the one or more speakers of the mobile device150. In another example, the representation of the notification is a predefined sequence of blinking LEDs of the mobile device150.

In some implementations, the notification indicates (1412) abortion of a transaction initiated by the user of the mobile device. InFIG.26C, for example, the user interface1320includes the message1322indicating that the transaction has been aborted. For example, the user aborts the transaction by actuating a coin return mechanism of the machine120. In another example, the user aborts the transaction by selection an abort affordance on the interface of the application140(not shown).

In some implementations, the notification indicates (1414) completion of a transaction between the user of the mobile device and the payment accepting unit. InFIG.26A, for example, the user interface1302includes the message1306indicating that completion of the transaction with the machine120initiated by the user of the mobile device150.

In some implementations, the notification indicating completion of the transaction at least includes (1416) an amount of the completed transaction. InFIG.26A, for example, the user interface1302includes prepaid balance1304which indicates that $1.00 has been deducted from the prepaid balance after performing a transaction with the machine120as compared to the prepaid balance inFIG.10C-10D(i.e., $9.00 inFIGS.10C-10Dand $8.00 inFIG.26A).

In some implementations, the mobile device sends (1418) at least a portion of the notification to a server via a second communication capability distinct from the first communication capability. Operation1260ofFIG.25B, for example, shows the mobile device150sending first transaction information to the server130for a completed transaction via the second communication capability (e.g., a long-range communication protocols such as Wi-Fi, CDMA, GSM, and/or the like). For example, the first transaction information at least includes the amount of the first completed transaction.

In some implementations, the first communication capability corresponds (1420) to a short-range communication protocol and the second communication capability corresponds to a long-range communication protocol. For example, the first communication capability of the mobile device150is a radio/transceiver means for communicating via one or more short-range communication protocols such as BLE, NFC, and/or the like (i.e., a non-persistent communication channel). For example, the second communication capability of the mobile device150is a radio/transceiver means for communicating via one or more long-range communication protocols such as Wi-Fi, CDMA, GSM, and/or the like.

In some implementations, the notification indicates (1422) failure of a transaction initiated by the user of the mobile device or a malfunction associated with the payment accepting unit. InFIG.26D, for example, the user interface1330includes the message1332indicating that there was an error with the transaction. For example, the transaction fails due to a vending jam or other malfunction. In another example, the payment accepting unit experiences a malfunction due to an open door or the like. In some implementations, at least a portion of the failure/malfunction notification is sent to the sever130and an alert is subsequently sent to the operator of the payment accepting unit (e.g., the machine120) by the server130.

It should be understood that the particular order in which the operations inFIGS.27A-27Bhave been described is merely for example purposes and is not intended to indicate that the described order is the only order in which the operations could be performed. One of ordinary skill in the art would recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein are also applicable in an analogous manner to the method1400described above with respect toFIGS.27A-27B.

FIG.28Aillustrates a block diagram of an offline-payment operated machine1500in accordance with some implementations. For example, the offline-payment operated machine1500(e.g., a form of the machine120) is an electro-mechanical machine capable of accepting currency (e.g., coins), which is not connected to any networks (e.g., telephone, cellular, or Wi-Fi). For example, the offline-payment operated machine1500is a washer or dryer at a laundromat, a parking meter, a car wash payment kiosk, or other offline-payment operated machine that dispenses goods and/or services.

InFIG.28A, the offline-payment operated machine1500includes a microswitch1502, a control unit1506, a power supply1508, a transistor1510, and an operation unit1512. The components of the offline-payment operated machine1500inFIG.28Aare examples and one of skill in the art will appreciate that various other components may be included in or excluded from the offline-payment operated machine1500.

InFIG.28A, the microswitch1502is a leveraged microswitch with lever1504. For example, the microswitch1502is a CHERRY BRAND™ microswitch with a normally open terminal (“NO”), a normally closed terminal (“NC”), and a common terminal. For example, the lever1504is incorporated into a coin slot of the offline-payment operated machine1500and is depressed whenever a coin slides down the coin slot into a coin reservoir of the offline-payment operated machine1500(not shown). For example, when the lever1504is depressed and the microswitch1502is wired in the NO configuration as shown inFIG.28A, the switch is closed. Continuing with this example, when the switch is closed, control unit1506receives a pulse (i.e., a payment acceptance signal) from the common terminal of the microswitch1502indicating depression of the lever1504from the reception of a US quarter (i.e., $0.25) or coin of another value.

In some implementations, when the control unit1506receives a preset sequence of payment acceptance signals indicative of a preset number of coins being received by the microswitch1502, the control unit1506initiates the operation of the offline-payment operated machine1500. For example, after receiving the preset sequence of payment acceptance signals (e.g., three pulses indicating reception of three US quarters), the control unit1506initiates operation of the offline-payment operated machine1500by applying current to the gate of the transistor1510which allows current to flow from the power supply1508to operation unit1512. For example, the operation unit1512is a motor of a dryer which begins spinning once current flows from the power supply1508.

InFIG.28A, payment module1520(e.g., a form of the adapter module100,FIGS.5and20) is configured to be installed in the offline-payment operated machine1500so as to retrofit the offline-payment operated machine1500to be able to accept electronic payments. In some implementations, the payment module1520includes all or some of the components included adapter module100inFIG.20such as processing unit750, memory760, a security unit755, and a communications unit770. In some implementations, the payment module1520also includes a first interface module1522, a second interface module1524, and a lead1536for drawing power from power supply1508of the offline-payment operated machine1500.

InFIG.28A, the first interface module1522is configured to sample payment acceptance signals from the microswitch1502(e.g., a coin receiving switch) via lead1532of the offline-payment operated machine1500. For example, the payment acceptance signals are indicative of a coin being received by the microswitch1502which depress lever1504. InFIG.28A, the second interface module1524is configured to sample control signals from the control unit1506of the offline-payment operated machine1500via lead1534that initiate an operation of the offline-payment operated machine (e.g., the application of current to the gate of the transistor1510) in response to receiving a preset sequence of payment acceptance signals from the microswitch1502(e.g., the coin receiving switch) indicative of the preset number of coins.

FIG.28Billustrates signals sampled by the payment module1520in accordance with some implementations. InFIG.28B, sample1550represents a preset sequence of payment acceptance signals sampled by the first interface module1522via lead1532that are sent from the microswitch1502to the control unit1506. For example, the preset sequence of payment acceptance signals indicative of the preset number of coins include pulses (i.e., payment acceptance signals)1552,1554,1556, and1558. For example, the leading edges of pulses1552,1554,1556, and1558at times1582,1584,1586, and1588indicate reception of a coin by microswitch1502which causes the switch to close when wired in the NO configuration as shown inFIG.28A. InFIG.28B, sample1570represents a control signal sampled by the second interface module1524via lead1534that is sent from the control unit1506to transistor1510. InFIG.28B, the sample1570includes a pulse1572that is sent from the control unit1506to transistor1510at time1590after receiving the preset sequence of payment acceptance signals from the microswitch1502(i.e., pulses1552,1554,1556, and1558).

FIGS.29A-29Billustrate a flowchart diagram of a method of retrofitting an offline-payment operated machine to accept electronic payments in accordance with some implementations. In some implementations, the method1600is performed by a payment module with one or more processors and memory. In some implementations, the payment module also includes a short-range communication capability corresponding to a short-range communication protocol (e.g., a non-persistent communication channel such as BLE, NFC, and/or the like), where the short-range communication capability is configured to communicate with one or more mobile devices, where each of the one or more mobile devices is configured with a complimentary short-range communication capability and a long-range communication capability corresponding to a long-range communication protocol (e.g., Wi-Fi, CDMA, GSM, and/or the like).

In some implementations, the payment module is coupled with an offline-payment operated machine (e.g., the payment accepting unit120,FIGS.5and19(sometimes also herein called “machine120”), or the offline-payment operated machine1500,FIG.28A) such as dryer or washer in a laundromat, a parking meter, a car wash payment kiosk, or the like. In some implementations, the offline-payment operated machine includes a coin receiving switch (e.g., the microswitch1502,FIG.28A) and a control unit (e.g., the control unit1506,FIG.28A). In some implementations, the payment module further includes: (A) a first interface module (e.g., the first interface module1522,FIG.28A) configured to sample payment acceptance signals from the coin receiving switch of the offline-payment operated machine, where the signals are indicative of a coin being received by the coin receiving switch; and (B) a second interface module (e.g., the second interface module1524,FIG.28A) configured to sample control signals from the control unit of the offline-payment operated machine that initiate an operation of the offline-payment operated machine in response to receiving a preset sequence of payment acceptance signals from the coin receiving switch indicative of the preset number of coins. By sampling and storing these signals, the payment module1520is able to simulate operation of a respective coin receiving switch in response to receiving the correct/preset number of coins so as to trigger operation of the offline-payment operated machine in response to completion of an electronic payment.

For example, in some implementations, the method1600is performed by the adapter module100(FIGS.5and20) or payment module1520(FIG.28A). In some implementations, the method1600is governed by instructions that are stored in a non-transitory computer readable storage medium (e.g., the memory760,FIG.20) and the instructions are executed by one or more processors (e.g., the processing unit750,FIG.20) of the payment module. Optional operations are indicated by dashed lines (e.g., boxes with dashed-line borders).

In some implementations, the payment module detects (1602), via the first interface module, a preset sequence of payment acceptance signals from the coin receiving switch that causes the control unit to initiate the operation of the offline-payment operated machine, where the preset sequence of payment acceptance signals are indicative of a preset number of coins received by the coin receiving switch. For example, with reference toFIGS.28A-28B, the first interface module1522of the payment module1520samples payment acceptance signals via lead1532from the microswitch1502to the control unit1506. For example, each of the payment acceptance signals is indicative of reception of a coin by the microswitch1502. Continuing with this example, the second interface module1524of the payment module1520samples control signals via lead1534from the control unit1506to the transistor1510. The payment module1520detects a preset sequence of payment acceptance signals from the microswitch1502that causes the control unit1506to apply a current to the gate of the transistor1510(e.g., the control signals). For example, the preset sequence of payment acceptance signals is indicative of a preset number of coins received by the microswitch1502to cause operation of the offline-payment operated machine1500. For example, the application of current to the gate of the transistor1510allows current to flow from the power supply1508to the operation unit1512so that the operation. For example, the operation unit1512is a motor of a dryer which begins spinning once current flows from the power supply1508.

In some implementations, the payment module determines (1604) the predefined signal sequence to emulate the preset sequence of payment acceptance signals from the coin receiving switch. In some implementations, after detecting the preset sequence of payment acceptance signals that causes the control unit1506to initiate the operation of the offline-payment operated machine1500, the payment module1520determines a predefined signal sequence to emulate the preset sequence of payment acceptance signals. In some implementations, the money value associated with each pulse in the preset sequence of payment acceptance signals from the microswitch1502, indicative of the preset number of coins to initiate the operation of the offline-payment operated machine1500, is a default currency (e.g., USD) and amount (e.g., $0.25) set in the firmware of the payment module1520. In some implementations, the money value associated with the each pulse in the preset sequence of payment acceptance signals from the microswitch1502, indicative of the preset number of coins to initiate the operation of the offline-payment operated machine1500, is set by the server130and can be changed remotely by using the mobile device150as a communications bridge to send information indicating the value of a pulse from the server130to the mobile device150via the second communication capability (e.g., GSM, CDMA, or Wi-Fi) and forwarding the information from the mobile device to the payment module1520via the first communication capability (e.g., BLE). For instance, in most cases, each pulse is US $0.25.

In some implementations, determining the predefined signal sequence includes (1606) at least one of: identifying a count of pulses in the present sequence of payment acceptance signals; identifying amplitude of pulses in the present sequence of payment acceptance signals; identifying shape of pulses in the present sequence of payment acceptance signals; and identifying an interval between pulses. In some implementations, after detecting the preset sequence of payment acceptance signals (e.g., the sample1550,FIG.28B), the payment module1520determines a predefined signal sequence to emulate the preset sequence of payment acceptance signals by identifying a count of pulses in the preset sequence of payment acceptance signals, an interval between pulses in the preset sequence of payment acceptance signals, the shape of pulses in the preset sequence of payment acceptance signals, and an amplitude of pulses in the preset sequence of payment acceptance signals.

The payment module receives (1608) a request via the short-range communication capability from a respective mobile device to perform an operation of the offline-payment operated machine. For example, with reference toFIG.8C, the payment module1520(FIG.28A) receives the AuthGrant from the mobile device150via the short-range communication capability (e.g., BLE) indicating that the user of the mobile device150wishes to perform the operation of the offline-payment operated machine1500(FIG.28A). For example with reference to operation1012inFIG.23, the payment module1520(FIG.28A) receives an authorization grant token from the mobile device150via the short-range communication capability (e.g., BLE) indicating that the user of the mobile device150wishes to perform the operation of the offline-payment operated machine1500(FIG.28A).

The payment module validates (1610) the request. Validation of the request indicates (1612) that the respective mobile device is authorized to initiate payment for the operation by a remote server via the long-range communication capability. In some implementations, the payment module1520validates the request from the mobile device150by determining whether the AuthGrant or the authorization grant token includes a valid authorization code.

In accordance with a determination that the request is valid, the payment module causes (1614) the payment operated machine to perform the operation by issuing a predefined signal sequence to the control unit, where the predefined signal sequence emulates a signal sequence that would be issued by the coin receiving switch in response to receiving a preset number of coins. For example, with reference toFIG.28B, the payment module1520issues a predefined signal sequence with first interface module1522to the control unit1506that emulates sample1550inFIG.28B. Continuing with this example, in response to receiving the predefined signal sequence from the payment module1520control unit1506causes initiation of the operation of the offline-payment operated machine1500by applying current to the gate of the transistor1510which allows current to flow from the power supply1508to operation unit1512. In some implementations, the control unit1506causes initiation of the operation by setting a timer to an amount of time corresponding to the preset number of coins whereby current flows to the gate of the transistor1510for the set amount of time. For example, the preset number of coins is a number of a coins required to run the offline-payment operated machine1500by for a default amount of time and subsequent coins may be added to extend the amount of time that the offline-payment operated machine1500by will run. In some implementations, the preset number of coins is a number of a coins required to cause the offline-payment operated machine1500to dispense a purchased item, such as laundry detergent.

Alternatively, in some implementations, in accordance with a determination that the request is valid, the offline-payment operated machine1500displays credit to the user (e.g., via one of the displays122or124shown inFIG.19) and the user interacts with the input mechanisms of the offline-payment operated machine1500120(e.g., via the buttons126or a touch screen display124shown inFIG.19) to perform the operation of the machine. For example, if the offline-payment operated machine1500is a dryer, the user of the mobile device150selects the appropriate spin cycle via input mechanisms of the dryer, and when the user of the mobile device150selects a start/run input mechanism of the dryer, control unit1506of the dryer causes initiation of the operation of the dryer (e.g., starting a motor that corresponds to operation unit1512inFIG.28A).

In some implementations, prior to sending the operation information and after causing the offline-payment operated machine to perform the operation by issuing the predefined signal sequence to the control unit, the payment module obtains (1616) a notification from the offline-payment operated machine indicating initiation of the operation of the offline-payment operated machine and the preset number of coins. For example, after issuing the preset signal sequence to control unit1506, the payment module1520(FIG.28A) obtains a notification indicating that the control unit1506sent control signals to initiate operation of the offline-payment operated machine1500in response to receiving the predefined signal sequence. For example, the notification is obtained by the second interface module1524(e.g., the sample1570,FIG.28B) sampling controls signals sent by control unit1506(e.g., application of current to the gate of the transistor1510which allows current to flow from the power supply1508to operation unit1512).

In response to receiving the notification, the payment module (1618): generates the operation information based at least in part on the notification; and stores the generated operation information in the memory. For example, after obtaining the notification, the payment module1520(FIG.28A) generates operation information corresponding to performance of the operation and the preset number of coins associated with the predefined signal sequence (e.g., the amount required to initiate operation of the offline-payment operated machine1500) and stores the operation information in memory local to the payment module1520(e.g., the memory760,FIG.20).

In some implementations, the payment module sends (1620) operation information corresponding to the operation to the respective mobile device via the short-range communication capability. For example, after operation1618, the payment module1520(FIG.28A) sends the operation information to the mobile device150via the first communication capability of the mobile device150such as a radio/transceiver means for communicating via one or more short-range communication protocols such as BLE, NFC, and/or the like (i.e., a non-persistent communication channel)

It should be understood that the particular order in which the operations inFIGS.29A-29Bhave been described is merely for example purposes and is not intended to indicate that the described order is the only order in which the operations could be performed. One of ordinary skill in the art would recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., the method1700inFIG.30) are also applicable in an analogous manner to the method1600described above with respect toFIGS.29A-29B.

FIG.30illustrates a flowchart diagram of a method1700of enabling a payment operated machine to accept electronic payments in accordance with some implementations. In some implementations, the method1700is performed by an offline-payment operated machine (e.g., the payment accepting unit120,FIGS.5and19(sometimes also herein called “machine120”), or the offline-payment operated machine1500,FIG.28A) such as dryer or washer in a laundromat, a parking meter, a car wash payment kiosk, or the like.

In some implementations, the offline-payment operated machine includes a control unit (e.g., the control unit1506,FIG.28A), memory, and a coin receiving switch (e.g., the microswitch1502,FIG.28A). In some implementations, the offline-payment operated machine also includes a short-range communication capability corresponding to a short-range communication protocol (e.g., a non-persistent communication channel such as BLE, NFC, and/or the like), where the short-range communication capability is configured to communicate with one or more mobile devices, where each of the one or more mobile devices is configured with a complimentary short-range communication capability and a long-range communication capability corresponding to a long-range communication protocol (e.g., Wi-Fi, CDMA, GSM, and/or the like). For example, in some implementations, the method1700is performed by the machine120, (FIGS.5and19). In some implementations, the method1700is governed by instructions that are stored in a non-transitory computer readable storage medium and the instructions are executed by the control unit of the offline-payment operated machine.

The offline-payment operated machine receives (1702) a request via a short-range communication capability from a respective mobile device to perform an operation of the offline-payment operated machine. For example, with reference toFIG.8C, the payment module1520(FIG.28A) receives the AuthGrant from the mobile device150via the short-range communication capability (e.g., BLE) indicating that the user of the mobile device150wishes to perform the operation of the offline-payment operated machine1500(FIG.28A). For example with reference to operation1012inFIG.23, the payment module1520(FIG.28A) receives an authorization grant token from the mobile device150via the short-range communication capability (e.g., BLE) indicating that the user of the mobile device150wishes to perform the operation of the offline-payment operated machine1500(FIG.28A).

The offline-payment operated machine validates (1704) the request. Validation of the request indicates (1706) that the respective mobile device is authorized to initiate payment for the operation by a remote server via the long-range communication capability. In some implementations, the payment module1520validates the request from the mobile device150by determining whether the AuthGrant or the authorization grant token includes a valid authorization code.

In accordance with a determination that the request is valid, the offline-payment operated machine performs (1708) the operation by issuing a predefined signal sequence to the control unit, where the predefined signal sequence emulates a preset number of coins received by the coin receiving switch. For example, in accordance with a determination that the request is valid, the offline-payment operated machine or a component thereof issues a predefined signal sequence to the control unit1506that emulates sample1550inFIG.28B. Continuing with this example, in response to receiving the predefined signal sequence from the payment module1520, control unit1506causes initiation of the operation of the offline-payment operated machine1500by applying current to the gate of the transistor1510which allows current to flow from the power supply1508to operation unit1512. In another example, in accordance with a determination that the request is valid, the control unit1506causes initiation of the operation of the offline-payment operated machine1500by applying current to the gate of the transistor1510which allows current to flow from the power supply1508to operation unit1512.

It should be understood that the particular order in which the operations inFIG.30have been described is merely for example purposes and is not intended to indicate that the described order is the only order in which the operations could be performed. One of ordinary skill in the art would recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., the method1600inFIGS.29A-29B) are also applicable in an analogous manner to the method1700described above with respect toFIG.30.

MISCELLANEOUS

It should be noted that relative terms are meant to help in the understanding of the technology and are not meant to limit the scope of the invention. Similarly, unless specifically stated otherwise, the terms used for labels (e.g., “first,” “second,” and “third”) are meant solely for purposes of designation and not for order or limitation. The term “short” in the phrase “short-range” (in addition to having technology specific meanings) is relative to the term “long” in the phrase “long-range.”

The terms “may,” “might,” “can,” and “could” are used to indicate alternatives and optional features and only should be construed as a limitation if specifically included in the claims.

It should be noted that, unless otherwise specified, the term “or” is used in its nonexclusive form (e.g., “A or B” includes A, B, A and B, or any combination thereof, but it would not have to include all of these possibilities). It should be noted that, unless otherwise specified, “and/or” is used similarly (e.g., “A and/or B” includes A, B, A and B, or any combination thereof, but it would not have to include all of these possibilities). It should be noted that, unless otherwise specified, the terms “includes” and “has” mean “comprises” (e.g., a device that includes, has, or comprises A and B contains A and B, but optionally may contain C or additional components other than A and B). It should be noted that, unless otherwise specified, the singular forms “a,” “an,” and “the” refer to one or more than one, unless the context clearly dictates otherwise.

It is to be understood that the inventions, examples, and implementations described herein are not limited to particularly exemplified materials, methods, and/or structures. It is to be understood that the inventions, examples, and implementations described herein are to be considered preferred inventions, examples, and implementations whether specifically identified as such or not.

The terms and expressions that have been employed in the foregoing specification are used as terms of description and not of limitation, and are not intended to exclude equivalents of the features shown and described. While the above is a complete description of selected implementations of the present invention, it is possible to practice the invention using various alternatives, modifications, adaptations, variations, and/or combinations and their equivalents. It will be appreciated by those of ordinary skill in the art that any arrangement that is calculated to achieve the same purpose may be substituted for the specific embodiment shown. It is also to be understood that the following claims are intended to cover all of the generic and specific features of the invention herein described and all statements of the scope of the invention that, as a matter of language, might be said to fall therebetween.