Patent Grant
11501217
This invention relates to mobile devices and related systems.
A user may communicate information directly from a card to a memory location of a mobile device via a contactless communication channel between the card and the mobile device. Accordingly, for example, a mobile device may store information (e.g., payment information) associated with one or more cards (e.g., one or more payment cards) that have been presented within a proximity to the mobile device. In so doing, for example, a mobile device may be a mobile wallet having multiple accounts (e.g., payment, identification, and travel accounts) stored within a memory of the mobile wallet where each account may be recalled from a memory of the mobile wallet at the user's request to perform a function (e.g., to complete a payment transaction).
A mobile device may detect the presence of a card that is brought within a communication distance of a contactless interface of the mobile device. A card may, for example, provide RFID capability that may communicate with an RFID device of a mobile device when the card comes within a communication distance of the mobile device. Accordingly, for example, a card type may be identified by the mobile device and information associated with the card type may be communicated from the card to the mobile device. Information received by the mobile device from the card may be autonomously categorized by the mobile device in accordance with a card type and the information may be stored and displayed to a user in accordance with the categorization.
A card (e.g., a non-powered payment card) may, for example, communicate one, two, and/or three tracks of magnetic stripe data to a mobile device via a contactless interface. Accordingly, for example, a processor of a mobile device may identify a card type (e.g., a payment card) by analyzing the magnetic stripe data received from the card. A processor of a mobile device may, for example, determine an account type (e.g., credit or debit) that may be associated with the non-powered payment card by inspection of magnetic stripe data (e.g., account number) received from the non-powered card.
A powered card may, for example, communicate information to a contactless interface of a mobile device. In so doing, for example, additional information (e.g., information presented in discretionary data) may be identified by a processor of the mobile device to determine that a detected card is a powered card having increased capability.
Accordingly, for example, a user of a powered card may select a feature (e.g., pay with credit) on the powered card and a processor of a mobile device may detect that such a feature is selected based upon an analysis of the information received from the powered card.
A mobile device may, for example, validate a payment card. For example, a mobile device may request entry of a PIN after a payment card is presented to the mobile device. Once a PIN is entered, a mobile device may, for example, access a server associated with the issuing entity to validate the PIN. A processor of a mobile device may, for example, compare the PIN entry against memory contents of the mobile device to locally validate the entered PIN.
Data received from a card may, for example, be encrypted. Accordingly, for example, data received from a card may be stored in an encrypted state and decrypted upon receipt of a decryption key. A decryption key may, for example, be received from a sponsoring entity of the card (e.g., a card issuer's server). Decrypted data may, for example, be destroyed such that each usage of encrypted data may require a decryption key prior to usage. Alternately, for example, decrypted data may be stored within a protected memory of the mobile device and kept for future use.
A user of a mobile device may, for example, extract physical, or real, cards (e.g., payment, identification, travel, and rewards cards) from the user's physical wallet or purse and may convert each physical card into a virtual equivalent card that resides electronically within the mobile device. Accordingly, for example, each physical card (e.g., a powered card or a non-powered card) may be brought within a proximate, or touching, relationship with a mobile device to create a contactless communication channel. Card information (e.g., cardholder data, card data, and card configuration data) may, for example, be communicated by the card to the mobile device via such a contactless communication channel. In so doing, for example, a virtual card may be created within the mobile device that is both visibly and functionally equivalent to its physical counterpart.
A non-powered card may, for example, be virtually rendered onto a display of a mobile device in a manner that resembles its physical counterpart. Card and cardholder information may, for example, be communicated by the non-powered card to the mobile device and rendered onto a virtual card that may be displayed by a processor of the mobile device. Accordingly, for example, the functionality of the physical card (e.g., a non-powered payment card) may be imparted to the virtual card by the mobile device when the mobile device communicates information (e.g., payment information) that may be associated with the non-powered payment card. As per one example, a mobile device may communicate payment information associated with a virtual card that may be displayed on a GUI of the mobile device when the mobile device is brought within a communication distance of a merchant terminal to complete a purchase transaction (e.g., an RFID device of the mobile device may communicate with an RFID device of a merchant terminal to exchange payment information between the mobile device and the merchant terminal to complete the purchase transaction). As per another example, a mobile device may communicate payment information associated with a virtual card when the mobile device accesses a network entity (e.g., a payment server) via a wireless network (e.g., a cellular network or a Wi-Fi hotspot) to complete a purchase transaction using the communicated payment information.
A powered card may, for example, be virtually rendered onto a display of a mobile device in a manner that resembles its physical counterpart. A powered card may, for example, be virtually rendered onto a display of a mobile device in a manner that provides user interface functionality that may be associated with the physical counterpart. A powered card may, for example, communicate configuration information (e.g., button placement and associated functionality, display placement and associated functionality and input/output functionality) to a processor of a mobile device and the processor may render such a configuration onto a virtual card such that the configuration of the virtual card provides substantially identical functionality as compared to its physical counterpart.
As per one example, a powered card (e.g., a powered payment card) may include one or more buttons that when activated determine a method of payment to be used to complete a transaction (e.g., pressing one button may invoke a credit payment transaction while pressing another button may invoke a debit payment transaction). Accordingly, for example, a virtual card may be rendered onto a display of a mobile device that includes the same functionality, such that when one virtual button is touched on the virtual card, a credit payment message is communicated by the mobile device and when another virtual button is touched on the virtual card, a debit payment message is communicated by the mobile device.
As per another example, a powered card may be programmed for a particular feature by pressing a button on the powered card associated with that feature. Accordingly, for example, a powered card may communicate information associated with a selected feature to a mobile device and a processor of the mobile device may render a virtual card on a GUI of the mobile device in accordance with the selected feature. In so doing, for example, a powered card may be selected as a powered payment card with a debit feature and the selected feature may be communicated to a mobile device (e.g., the debit feature may be communicated to a mobile device within a discretionary data field of a magnetic stripe message). The resulting virtual payment card rendered onto a display of the mobile device may, for example, provide a virtual payment card having a fixed payment feature (e.g., a fixed debit payment feature).
A mobile device may, for example, challenge a user of the mobile device to enter a password (e.g., a PIN) that may be associated with a card. A mobile device may, for example, require a password before a virtual card may be created and stored within the mobile device. A mobile device may, for example, allow a virtual card to be created and stored within a mobile device, but may challenge a user of the mobile device to enter a password associated with the virtual card before it can be recalled from a memory of the mobile device and used (e.g., used to complete a purchase transaction).
A user may, for example, participate in the personalization of a virtual card that may be stored within a memory of a mobile device. A mobile device may, for example, store various logos (e.g., issuer logos, network brand logos, and merchant logos) within a memory of the mobile device and may allow a user of the mobile device to use a GUI of the mobile device to personalize an appearance of a virtual card with such logos. Accordingly, for example, a user may perform drag-and-drop operations, alphanumeric entry operations, and any other operation to personalize an appearance of a virtual card stored within a memory of the mobile device.
A processor of a mobile device may, for example, organize two or more virtual cards for display on a GUI of the mobile device. A mobile device may, for example, keep track of a number of usages of one or more virtual cards and may sort such virtual cards within a list of displayed virtual cards so that a user may easily access his or her most used virtual card from a top of the displayed list. A mobile device may, for example, track a location of a user of the mobile device and organize a list of virtual cards in accordance with such a location. Accordingly, for example, a user may be shopping within a general merchandise store (e.g., Target), a processor of the user's mobile device may track the user's position to the Target store and the processor of the user's mobile device may display a virtual card (e.g., a Target gift card) at the top of a displayed list of virtual cards based upon the user's location. In so doing, for example, a virtual card most pertinent to the user's location may be sorted to the top of a displayed list of virtual cards for easy and convenient access by the user.
A user may, for example, select one virtual card from a list of virtual cards presented by a GUI of a mobile device and may perform one of many operations on the selected virtual card. A user may, for example, conduct a purchase transaction using a virtual payment card selected from a list of virtual cards.
Accordingly, for example, a user may place a mobile device within a vicinity of a merchant terminal and may communicate payment information associated with a selected payment card to the merchant terminal. As per another example, payment information associated with a selected virtual card may be communicated to a network entity (e.g., a payment server or an issuer's server) by the mobile device to complete a purchase transaction.
A mobile device may, for example, receive an electronic receipt for the purchase transaction either via a communication channel established between the mobile device and the merchant terminal or via other communication channels (e.g., text messaging or email exchange with a network entity such as a payment server). A user may, for example, view documents (e.g., receipts or bank statements) that may be associated with a virtual card. Accordingly, for example, a mobile device may collect and store documents associated with a virtual payment card and may display the associated documents upon request from the user. A GUI of a mobile device may, for example, allow a user to annotate documents that may be associated with a virtual card (e.g., a user may make a note that may be electronically attached to an electronic receipt that may be associated with a virtual payment card).
Other cards (e.g., other virtual cards) may be associated with a selected virtual card and those associations may be viewed from a GUI of the mobile device. For example, a payment card may be associated with a rewards card, such that in response to a request from a user of a mobile device, a processor of the mobile device may display the associations to the payment card and may use the associated virtual cards in support of a purchase transaction (e.g., the associated rewards card may be used during a payment transaction conducted with the selected virtual payment card so that the rewards account may accrue rewards points for the purchase transaction).
A mobile device may, for example, allow a user of the mobile device to cancel an account that may be associated with a virtual card stored within the mobile device. Accordingly, for example, a virtual payment card may be stored within a mobile device and may be associated with a payment account that is administered by an issuing entity of the payment account. A mobile device may, for example, communicate with such an issuing entity to cancel a payment account that may be associated with a virtual payment card stored within the mobile device. A mobile device may, for example, negotiate with other issuing entities to determine when new payment card offers may be available and to allow a user of the mobile device to accept such payment card offers. Once accepted, a user of a mobile device may conduct other transactions with the newly accepted payment card offers (e.g., account balance(s) associated with existing virtual cards may be transferred to the newly accepted payment card via a request made by the mobile device and an issuing server).
Any mobile device, such as a laptop computer, a mobile telephonic device (e.g., a cellular phone), a PDA, an MP3 player, or a positioning device (e.g., a GPS) may be a mobile wallet. Accordingly, for example, a mobile device may accept payment and other information from any payment card, store and display such information as a virtual card on a GUI of the mobile device, communicate such payment information via a wired and/or a wireless network, complete a settlement process with network entities (e.g., an issuer or a payment server) on such a network, and provide results (e.g., an electronic receipt) of the completed purchase transaction to a display of the mobile device.
A mobile device may include a contactless communication device. Accordingly, for example, a mobile device may communicate with any card having contactless communication capability. For example, a card (e.g., a non-powered card) may include a near-field communication device (e.g., an RFID tag) that may communicate with a contactless communication device of a mobile device to form a two-way communication channel between the card and the mobile device. In so doing, for example, a non-powered card may communicate one, two, and/or three tracks of magnetic stripe information to a mobile device before and/or during a purchase transaction conducted by the mobile device.
A card (e.g., a powered card) may include a near-field communication device (e.g., an RFID) that may communicate with a contactless communication device of a mobile device. A powered card may, for example, include a battery, a processor, memory, and a manual input interface (e.g., one or more buttons) that may allow a user of the powered card to programmably communicate information to a mobile device. For example, a powered payment card may include a feature associated with a button that allows a user to, for example, pay with credit or pay with debit.
Accordingly, for example, a powered payment card may communicate such a payment selection within discretionary data fields of one or more tracks of magnetic stripe data.
A powered card may, for example, include circuitry to simulate touch (e.g., a capacitance change) in order to form a contactless communication channel with a mobile device. Accordingly, for example, a powered card may be pressed against a touch-sensitive display of a mobile device and information may be communicated by the powered card to the mobile device through a series of card-simulated touches that may be detected by the touch-sensitive display of the mobile device and processed by a processor of the mobile device as data communicated by the powered card.
A powered card may, for example, include a light sensor to form a contactless communication channel with a mobile device. Accordingly, for example, a powered card may be pressed against a display of a mobile device and information may be communicated from the mobile device to the powered card through a series of light pulses generated by the display of the mobile device. A frequency, pulse width, and/or a pulse intensity of light pulses may, for example, be detected by a processor of a powered card as data communicated by a mobile device.
A powered card may, for example, include a light source (e.g., an LED) to form a contactless communication channel with a mobile device.
Accordingly, for example, a powered card may emit varying light pulses from an LED that may be detected by a motion-capture device (e.g., a camera) of a mobile device as data communicated by the powered card. A powered card may, for example, include sound emission capabilities that may be detected by a microphone of a mobile device as data communicated by the powered card through a contactless communication channel. A mobile device may, for example, include sound emission capabilities that may be detected by a microphone of a powered card as data communicated by the mobile device through a contactless communication channel.
The principles and advantages of the present invention can be more clearly understood from the following detailed description considered in conjunction with the following drawings, in which the same reference numerals denote the same structural elements throughout, and in which:
Mobile device 100 may include audio processing devices (e.g., microphone 108 and speaker 110). Accordingly, for example, mobile device 100 may receive voice commands from a user via microphone 108 and may process such commands to perform a function. For example, a user may place mobile device 100 into a desired operational mode by speaking a command into microphone 108 that is associated with the desired operational mode. In so doing, for example, mobile device 100 may engage in hands-free operation by receiving voice commands via microphone 108 and performing functions associated with the received voice commands.
Mobile device 100 may receive data input via microphone 108. For example, a voice-band modem may generate signals in a voice-band frequency range that may be received by microphone 108. A processor of mobile device 100 may interpret the received audible information as data signals and may process the data signals as, for example, data values and/or control data input.
Mobile device 100 may include camera 102. Camera 102 may capture one or more frames of video data and store the video data within a memory of mobile device 100. Accordingly, for example, a processor of mobile device 100 may receive one or more frames of video information via camera 102 and may process the video information as data values and/or control data input. In so doing, for example, mobile device 100 may receive optical information that is sensed by camera 102 during a series of one or more video capture events that produce one or more frames of video information. The one or more frames of video information may contain one or more data elements (e.g., pixels) having properties (e.g., color, intensity, or contrast) that may be interpreted by a processor of mobile device 100 as data values and/or control data.
Mobile device 100 may include manual input interface 112. Manual input interface 112 may, for example, include keys and/or buttons that may be sensitive to manual input, such as a touch or an application of pressure. Accordingly, for example, a user of mobile device 100 may enter information into mobile device 100 via manual interface 112 to cause a processor of mobile device 100 to enter a particular mode of operation. Manual interface 112 may, for example, be used for data entry (e.g., dialing a phone number or entering data as may be requested by mobile device 100) during a particular mode of operation of mobile device 100.
Mobile device 100 may include display 104. Display 104 may provide visible information that may be utilized by a user during interaction with mobile device 100. A portion or all of display 104 may be touch sensitive such that objects making contact with display 104 or objects coming within a proximity of display 104 may be detected by a processor of mobile device 100. Accordingly, for example, mobile wallet graphical user interface 106 may be provided by display 104 so that graphical information may be displayed to solicit and/or receive data entry from a user. In so doing, for example, touch-sensitive graphical user interface devices such as radio buttons, textual input boxes, virtual buttons, pull-down menus, and navigational tools may be used for data entry to initiate, change, and/or support functions performed by mobile device 100.
Display 104 may, for example, display graphical objects that may interact with a user of mobile device 100. Accordingly, for example, a virtual card (e.g., a virtual payment card) may be rendered onto display 104 having interactive components associated with such a virtual payment card. In so doing, for example, a virtual payment card displayed by display 104 may itself include a virtual user interface (e.g., one or more virtual buttons) that may be sensitive to touch or proximity. Such virtual buttons may be associated with a feature (e.g., one or more tracks of magnetic stripe information may be communicated by the mobile device when a button is activated). In so doing, for example, a feature activated on a virtual payment card displayed by display 104 may cause mobile device 100 to behave like a payment card (e.g., one or more tracks of magnetic stripe information may be communicated by mobile device 100 when a virtual button of a virtual payment card of display 104 is activated).
Architecture 150 may include one or more displays 154. Display 154 may, for example, be touch-sensitive. Accordingly, for example, display 154 may be utilized for alphanumeric data entry using virtual buttons that may be rendered onto touch-sensitive portions of display 154. In so doing, for example, touching virtual buttons that may be associated with alphabetic and numeric characters of display 154 may be detected by processor 158 as alphanumeric data entry.
Alphanumeric entry boxes may, for example, be rendered onto display 154. A user may, for example, activate a cursor within such an alphanumeric entry box by touching an area within the alphanumeric entry box. A user may utilize user interface 152 and/or a virtual keypad rendered onto display 154 to select alphanumeric characters to be placed within the alphanumeric entry box having a character position identified, for example, by an activated cursor within the alphanumeric entry box. In so doing, for example, processor 158 may receive alphanumeric characters as typed into a alphanumeric entry box of display 154 and may use such alphanumeric characters as data input.
Display 154 may, for example, render a virtual representation of a card (e.g., one or more virtual payment cards stored within memory 160). Accordingly, for example, information (e.g., payment card number, cardholder name, bank logos and issuer identification) may be stored within memory 160 and rendered onto display 154 as a virtual representation of a card. In so doing, for example, virtual interactive objects (e.g., buttons, displays, light sources and light sensors) that may be associated with a virtual card on display 154 may be utilized through interaction with display 154 just as if the virtual card were physically present.
Display 154 may, for example, provide data output from architecture 150. For example, display 154 may communicate data using a series of light pulses. Accordingly, for example, processor 158 may cause one or more portions of display 154 to produce light pulses having varying characteristics (e.g., duration, intensity, and frequency) that may communicate information via such light pulses. In so doing, for example, a device that may be sensitive to light pulses may receive information communicated by display 154 via light pulses having varying characteristics. Display 154 may, for example, communicate data using visual information that may be substantially static (e.g., a barcode).
Architecture 150 may include one or more transceivers 156. Transceiver 156 may communicate information to and/or may receive information from one or more devices. Transceiver 156 may, for example, communicate via a wireless interface with one or more cellular stations of a mobile network. Accordingly, for example, transceiver 156 may allow a mobile device (e.g., mobile device 100 of
Transceiver 156 may, for example, communicate via a wireless interface with one or more mobile devices directly. Accordingly, for example, transceiver 156 may communicate with another mobile device without first accessing a mobile network via a cellular station of the mobile network. As per another example, transceiver 156 may, for example, communicate via a wireless interface with one or more network devices (e.g., a wireless access point) directly. Accordingly, for example, a mobile device (e.g., mobile device 100 of
Architecture 150 may include contactless communication device 162, which may communicate via any one or more contactless communication methodologies, such as for example, near field communications (e.g., RFID), Bluetooth, touch simulation, light pulsing (e.g., via an LED), and electromagnetic data communication (e.g., via a dynamic magnetic stripe communications device). Accordingly, for example, contactless communication device 162 may be compatible with any contactless device, such as for example, an RFID enabled payment card and a contactless reader (e.g., a magnetic stripe reader or an NFC reader).
A non-powered card may, for example, communicate with contactless communications device 162. Contactless communication device 162 may, for example, establish a carrier field (e.g., an RF field) that may be modulated by a device (e.g., an RFID tag) of a non-powered payment card. In so doing, for example, an RFID tag of a non-powered payment card may derive operational power from an RF field provided by contactless communications device 162 and may communicate information (e.g., one, two, and/or three tracks of magnetic stripe data) to contactless communication device 162 by modulating the RF field produced by contactless communications device 162.
A powered card may, for example, communicate with contactless communication device 162. A powered card may, for example, include a processor, a battery, a memory, wireless communications devices (e.g., a dynamic magnetic stripe communications device or RFID) and other electronics (e.g., buttons, displays, light sources and light sensors) that may allow a user to interact with the powered card to perform one or more functions. Accordingly, for example, a powered card may be used to communicate specific information to contactless communication device 162 by selective interaction with the buttons of the powered card. In so doing, for example, a powered card may be used to interactively communicate magnetic stripe information (e.g., one, two, and/or three tracks of magnetic stripe data) to contactless communication device 162 by sending a signal to a processor of a powered card (e.g., by pressing a button on the powered card) to initiate such communications.
Contactless communication device 162 may receive variable data sets from a powered card based upon, for example, manual input provided to a powered card. For example, a button associated with an on-line purchase may be pressed on the powered card that causes a variable data set (e.g., account number and expiration date) to be communicated from the powered card to contactless communication device 162.
Discretionary data may, for example, be communicated by a powered card based upon which button was pressed on the powered card. In so doing, for example, a security code (e.g., “111”) may be communicated within a discretionary data field when a button associated with a particular feature (e.g., pay with credit) is pressed on the powered card. As per another example, a different security code (e.g., “222”) may be communicated within a discretionary data field when a button associated with a different feature (e.g., pay with debit) is pressed on the powered card. Accordingly, for example, processor 158 may identify what type of device may be in communication with contactless communication device 162 by analyzing the data communicated to contactless communication device 162.
Architecture 150 may include memory 160 and/or processor 158 may include internal memory. Accordingly, for example, application code may be stored within memory 160 and/or processor 158 and executed by processor 158 in support of functions performed by architecture 150. For example, an application (e.g., a mobile wallet graphical user interface) may be executed by architecture 150 and displayed onto display 154, which may be used to interact with a user of a mobile device (e.g., mobile device 100 of
Application data (e.g., virtual payment card data) may be stored within memory 160 and accessed by processor 158 during operation. For example, payment card data may be stored within memory 160 and recalled by processor 158 during a financial transaction being conducted by a mobile device (e.g., mobile device 100 of
Mobile wallet 202 may provide one or more transceivers that may communicate with one or more wired networks (e.g., IP network 212 and/or payment network 214) and/or one or more wireless networks (e.g., mobile network 210). Mobile wallet 202 may, for example, communicate with a cellular station over a wireless radio interface (e.g., a GSM air interface) that may be used by mobile wallet 202 to communicate information (e.g., voice and data) to cellular network access infrastructure 206 (e.g., one or more GSM base transceiver stations, base station controllers, and mobile switching centers). Persons skilled in the art will appreciate that cellular network access infrastructure 206 may utilize any multiple access architecture, such as for example, a code-division multiple access architecture and/or a time-division multiple access architecture.
Mobile wallet 202 may, for example, communicate with wireless access point 208 over a wireless interface (e.g., a Bluetooth interface or a Wi-Fi interface). Accordingly, for example, mobile wallet 202 may access one or more wired networks (e.g., IP network 212 and/or payment network 214) and/or one or more wireless networks (e.g., mobile network 210) without the need to first gain access to cellular network access infrastructure 206.
Any contactless device (e.g., a powered payment card or a non-powered payment card) may, for example, communicate with mobile wallet 202 via a contactless medium. Accordingly, for example, payment information (e.g., a payment account number and a card expiration date) may be communicated from a contactless device to mobile wallet 202. In so doing, for example, items for purchase on IP network 212 (e.g., the internet) may be accessed by a browser of mobile wallet 202 via an access point (e.g., wireless access point 208 or cellular network access infrastructure 206). Mobile wallet 202 may, for example, complete a purchase transaction by first obtaining required payment information from a contactless device, storing such payment information and communicating such payment information to network entities (e.g., payment server 216 and/or issuer 220).
Payment server 216 may, for example, contact issuer 220 via a network (e.g., payment network 214) with payment information received from mobile wallet 202 for authorization of a purchase. Once authorized, payment transaction information may be recorded onto a receipt that may be delivered to mobile wallet 202 via any one or more delivery options (e.g., via a short messaging service of mobile network 210 or an email delivery service of IP network 212). Mobile wallet 202 may allow a user to associate purchase categories (e.g., groceries, auto repair, or entertainment) to purchases transacted by the mobile wallet so that the user may receive a more detailed accounting of his or her expenditures on his or her receipt. Accordingly, for example, a user may enjoy a higher degree of integration such that a user may customize a level of detail provided on a receipt via mobile wallet 202.
A payment receipt may, for example, be provided to mobile wallet 202 as a proof-of-purchase object (e.g., a barcode) that may be provided to a display of mobile wallet 202 and read by other computing equipment (e.g., a barcode scanner) for proof-of-purchase confirmation.
A mobile wallet (e.g., mobile wallet 224) may, for example, include a contactless communication device (e.g., an RFID) that may initiate, sustain, and/or terminate contactless communication channel 228 with merchant terminal 218. Accordingly, for example, mobile wallet 224 may communicate payment information to merchant terminal 218 to complete a financial transaction. In so doing, for example, mobile wallet 224 may first receive payment information via a contactless communication channel from one or more contactless devices (e.g., a non-powered card), store the received payment information within a memory of mobile wallet 224, and forward the payment information onto merchant terminal 218 to complete a financial transaction. Accordingly, for example, payment information may be recalled from memory within mobile wallet 224, optionally authenticated and authorized by a user of mobile wallet 224 and communicated to merchant terminal 218 via contactless communication channel 228 to complete a financial transaction using merchant terminal 218. An electronic receipt may, for example, be generated by merchant terminal 218 and communicated to mobile wallet 224 via contactless communication channel 228.
Mobile wallet 302 and payment card 304 may each include a contactless communication device (e.g., RFID) that may communicate via a contactless communication channel that may be formed between mobile wallet 302 and payment card 304 after coming into proximity to one another. Payment card 304 may, for example, be tapped onto display 308 of mobile wallet 302 to establish a proximity relationship that forms a communication channel between payment card 304 and mobile wallet 302. As per another example, payment card 304 may be brought within a proximity distance (e.g., up to two inches) of mobile wallet 302 to establish a contactless communication channel between mobile wallet 302 and payment card 304.
A processor of mobile wallet 302 may, for example, execute application code that may generate a graphical user interface (GUI) onto display 308 of mobile wallet 302. Message 306 of such a GUI may invite a user of mobile wallet 302 to begin storage of card information (e.g., payment card information) by tapping one or more cards (e.g., one or more payment cards) against display 308. As per another example, by tapping a card (e.g., payment card 304) against mobile wallet 302, a processor of mobile wallet 302 may autonomously determine that card information associated with the tapped card is to be stored within a memory of mobile wallet 302 and a processor of mobile wallet 302 may then generate a mobile wallet GUI onto display 308 to autonomously download the card information and engage a user of mobile wallet 302 to administer any other activities that may be associated with such an information download.
A processor of mobile wallet 302 may, for example, autonomously determine a type of card that may be tapped against it. For example, a processor of mobile wallet 302 may receive payment card data that may be indicative of a non-powered payment card (e.g., payment card data received from a non-powered card may not provide a security code associated with the card). As per another example, a processor of mobile wallet 302 may receive data that may be indicative of a powered card (e.g., payment card data received may contain a dynamically generated security code). Payment card data received from a powered card may, for example, include a dynamic security code that may change depending upon a type of transaction being conducted (e.g., debit or credit transaction).
As per another example, payment card 304 may be a powered payment card that may include electronics to simulate a human touch (e.g., payment card 304 may generate a change in capacitance that may be sensed by display 308). Through a series of simulated touches, payment card 304 may communicate a series of data bits to display 308, which may then be processed by a processor of mobile wallet 302. In so doing, for example, a contactless communication channel may be established where data is transferred from payment card 304 to mobile wallet 302 via a series of simulated touches.
Payment card 304 may, for example, include a light sensor. Accordingly, for example, payment card 304 may be sensitive to light pulses generated within a region of display 308. The light sensor of payment card 304 may receive a series of light pulses, which may be construed by a processor of payment card 304 as data generated by mobile wallet 302. In so doing, for example, payment card 304 may receive an optical data stream represented by a series of light pulses generated by display 308. As such, a two-way communication channel may be formed, where simulated touches may generate a data stream from payment card 304 to mobile wallet 302 and light pulses may generate a data stream from mobile device 302 to payment card 304.
Card (e.g., payment card) information (e.g., track 1 and track 2 magnetic stripe data) may be communicated to the mobile device via a contactless communication channel and such information may be displayed within virtual card 402 as summary information that may be associated with the physical payment card. A payment card number communicated to a mobile device within a magnetic stripe message may, for example, include issuer identification as well as an issuing network identifier. Accordingly, for example, a processor of a mobile device may analyze the payment card number received from a physical payment card and may render a portion or all of the identifying information associated with the payment card number onto virtual card 402. In so doing, for example, issuer identification 404 as well as a logo representative of an issuing network identifier may be rendered onto virtual card 402. Additionally, a portion or all of payment card number 406 as well as cardholder's information (e.g., cardholder's name 408) may be rendered onto virtual card 402.
A portion or all of the card information received from a physical card may be stored within a memory of a mobile device. Alternately, for example, a portion or all of the card information received from a physical card may be collected by a mobile device and communicated by the mobile device to a remote server for storage and/or validation purposes. In so doing, for example, instead of storing payment card information within a memory of a mobile device, card identification 410 may, for example, be stored within a mobile device and used as an index identifier to look up payment information that may be stored within a remote server. A processor of a mobile device may generate card identification 410 and may display card identification 410 within an alphanumeric entry box. In so doing, for example, a user of a mobile device may either accept, or change, card identification 410 to a value that may later be used to remind the user of which physical payment card is associated with card identification 410 and to recall payment information associated with card identification 410 that may be remotely stored.
Activation of virtual button 508 may, for example, cause a processor of a mobile device to compare a PIN entered by a user of the mobile device to a PIN that may be associated with the payment card presented to the mobile device for storage. The PIN may, for example, be stored within protected memory of the mobile device, so that a processor of the mobile device may locally determine the validity of the PIN entered. Alternately, for example, the mobile device may communicate the PIN to, for example, the issuing bank for a remote validation of the PIN entered. Persons skilled in the art will appreciate that a user interface (e.g., a keypad or keyboard) of a mobile device may be used instead of virtual pin pad 506 to enter the one or more characters of a PIN.
Upon validation that the correct PIN was entered, virtual card 510 may be displayed. In particular, for example, account number 512 may be fully populated within virtual card 510 to indicate to a user of the mobile device that the PIN was correctly entered and to allow the user to compare account number 512 against an account number printed on the physical payment card of which virtual card 510 is a representation. Persons skilled in the art will appreciate that virtual payment cards may be stored within a mobile wallet without first requiring a user to validate the payment card using a PIN entry. An alternate form of validation (e.g., a security code) may, for example, be required for validation. As per another example, no validation may be required to store a virtual payment card onto a mobile wallet.
A user may, for example, press button 608 and then tap card 606 against display 604 of mobile wallet 602 to generate a contactless communication channel (an RFID communication channel) between card 606 and mobile wallet 602. Accordingly, for example, card 606 may communicate payment information (e.g., one, two and/or three tracks of magnetic stripe data) that may be associated with a feature selected by pressing button 608. In so doing, for example, card 606 may communicate information (e.g., within a discretionary data field) associated with a selected feature (e.g., a VISA debit payment feature).
Accordingly, for example, a user may have pressed a button on a powered payment card associated with a debit pay feature and may have communicated the debit pay feature (e.g., within a discretionary data field of a magnetic stripe message) to a mobile device via a contactless communication channel that may have been created between the powered payment card and the mobile device. In so doing, for example, a processor of a mobile device may analyze the debit pay feature received from the powered payment card and may render an indication (e.g., “Pay Now” identifier 714) onto virtual card 710 to indicate that virtual payment card 710 has been stored within the mobile device such that when used by a user of the mobile device to complete a payment transaction, authorizes an immediate deduction of funds from the user's payment account. Alphanumeric entry box 716 may, for example, allow the user to tag stored virtual card 710 with a card identifier that reminds the user of the debit functionality associated with virtual card 710.
A processor of a mobile device may, for example, analyze information received from a powered payment card (e.g., information received via a discretionary data field) and may determine that payment information received from the powered payment card may be associated with a credit feature (e.g., “Pay Later” feature 814). Accordingly, for example, a processor of a mobile device may use identifier 814 of virtual card 810 to signify such a credit payment feature.
Virtual card identifier 816 may, for example, be an editable card identifier to allow a user of a mobile device to store and recall virtual card 810 to/from a memory of a mobile device. Card identifier 816 may, for example, be used by a mobile device to access virtual card 810 from a remote location (e.g., a remote server) such that the mobile device need not store sensitive information that may be associated with virtual card 810 within the mobile device.
GUI 800 may, for example, allow an additional card to be associated with virtual card 810. A rewards card may, for example, be associated with a credit account that may be associated with virtual card 810. Accordingly, for example, rewards card information may be communicated to a mobile device by tapping the rewards card against portion 818 to generate a contactless communication channel (e.g., an RFID communication channel) between the rewards card and the mobile device. As per another example, an identification card (e.g., a driver's license) may be associated with virtual card 810. Accordingly, for example, identifying information (e.g., date of birth and a picture) associated with the holder of the identification card may be communicated to a mobile device and stored within the mobile device. In so doing, for example, stored identification information may be recalled from a memory of the mobile device to provide authentication information while completing a purchase transaction using the mobile device.
A user may, for example, select option 820 to allow card information to be scanned into a mobile device using a scanning device (e.g., a camera) of the mobile device. Accordingly, for example, a card (e.g., a driver's license) may be scanned into a mobile device by selecting radio button 820 and holding the driver's license in front of the mobile device while a snapshot of the driver's license is taken by a camera of the mobile device and stored in a memory location of the mobile device. A mobile device may alternately, for example, access identifying information (e.g., name, address, phone number, and picture) from a database (e.g., a motor vehicle database) that may be accessible from a network. Such information may be rendered onto a virtual identification card (e.g., a driver's license) that may be stored within a mobile device. In so doing, for example, user identification data may be recalled from a memory of a mobile device and rendered onto a display of the mobile device, so that a merchant may verify the validity of the user identification data when virtual card 810 is used to complete a purchase transaction in the presence of the merchant.
Card information may be communicated via programming portion 822. A powered card may, for example, provide touch simulation electronics and a light sensor such that when the powered card is placed against portion 822, a two-way contactless communication channel may be created. Accordingly, for example, information may be communicated from the powered card to the mobile device through a series of touch simulations generated by the powered card and sensed by a portion within portion 822 that is touch sensitive. In so doing, for example, a processor of a mobile device may construe a series of touch simulations as a series of data bits communicated by a powered card that may be indicative of information associated with the powered card. GUI 800 may, for example, provide a series of light pulses within portion 822 that may be received by a light sensor of the powered card and construed by a processor of the powered card as data communicated by the mobile device.
Information associated with a powered payment card may be uploaded for use by a mobile device by exchanging data with the powered payment card via data exchange areas 904 and 906. For example, a powered payment card may be pressed against upload area 902 so that a touch simulation device of the powered payment card aligns with data exchange area 904 and a light sensing device of the powered payment card aligns with data exchange area 906. Accordingly, for example, the powered payment card may communicate information to a processor of a mobile device by simulating a series of touches in data exchange area 904 and data may be communicated to the powered payment card by a processor of the mobile device by generating a series of light pulses in data exchange area 906. In so doing, for example, a mobile device and a powered payment card may exchange information so that payment card information may be stored within the mobile device.
Once payment card information is uploaded into a mobile device, GUI 900 of the mobile device may display a summary of the uploaded information in validation area 910. Accordingly, for example, one, two or three tracks of magnetic stripe information may be uploaded from a payment card into a mobile device via data exchange area 904 of upload area 902. A portion or all of the uploaded data may, for example, be rendered within validation area 910, so that a user of the mobile device may validate that the correct payment card information was uploaded and stored within the mobile device.
A user of a mobile device may, for example, customize a visual appearance of virtual card 1010 by utilizing any number of graphical user interface objects (e.g., list 1004 and alphanumeric input box 1012) that may be rendered by GUI 1000. A user may, for example, drag-and-drop logos from list 1004 onto virtual card 1010 to more clearly identify virtual card 1010. Accordingly, for example, a user may identify virtual card 1010 as a gift card (e.g., a Walmart gift card), using drag-and-drop operation 1008, having a particular network brand (e.g., a VISA network brand), using drag-and-drop operation 1006. A user may, for example, annotate virtual card 1010 using alphanumeric input box 1012 with any identifying information that may be useful to the user (e.g., information that may be used to recall virtual card 1010 from a memory of a mobile device).
A mobile device may, for example, disallow certain customizations that may conflict with virtual card 1010. Accordingly, for example, a mobile device may prevent a user from applying a different network logo than was previously communicated by a physical card to the mobile device. In so doing, for example, a mobile device may prevent a user from customizing virtual card 1010 as, for example, a M/C network brand, when a payment card number previously communicated from a payment card to a mobile device indicated that the payment card was, for example, a payment card having a VISA network brand.
A credit balance, for example, may be communicated by a gift card to a mobile device via a contactless communication channel generated between the gift card and the mobile device and may be displayed as account balance 1014 to represent an amount of credit that may be remaining on virtual card 1014. Virtual card 1010 may, for example, be used by a mobile device to complete a purchase transaction in which payment card information associated with virtual card 1010 may be communicated to a merchant terminal (e.g., communicated via an RFID communication channel) and an amount of the purchase may be communicated from the merchant terminal to the mobile device. Accordingly, for example, account balance 1014 may be updated (e.g., reduced) by the amount of the purchase and displayed so that a user of the mobile device may be updated as to an amount of credit remaining on virtual card 1010.
A user of a mobile device may, for example, purchase additional credit to be added to virtual card 1010. Accordingly, for example, account balance 1014 may be updated (e.g., increased) when an amount of credit is added to virtual card 1010. In so doing, for example, an amount of credit added to virtual card 1010 may be communicated (e.g., communicated via an RFID communication channel) to a mobile device by a merchant terminal and updated via account balance 1014 so that a user of the mobile device may receive up-to-date information relating to a credit balance that may be available on virtual card 1010. As per an example, a user may recall a virtual payment card from a memory of a mobile device, activate the payment card for use, and use the mobile device to purchase additional credit on virtual card 1010 using the activated payment card as the payment vehicle.
An account number may, for example, be communicated by a card to a processor of a mobile device that may identify the card as a particular card type (e.g., bank card, rewards card, identification card, healthcare card, travel card or airline card). Accordingly, for example, each virtual card stored within a memory of a mobile device may be assigned a category index by a processor of the mobile device and may then be rendered onto GUI 1100 in accordance with the category index assigned. As per another example, a user of a mobile device may assign a category index (e.g., card identification) to a virtual card after information associated with a corresponding physical card is communicated to the mobile device via a contactless communication channel.
One or more payment cards, for example, may be rendered onto GUI 1100 and each payment card may be aligned within category 1106. An ordering of each payment card in category 1106 may, for example, be established by a user of a mobile device via sort options 1102. A mobile device may, for example, maintain statistics (e.g., number of times each virtual payment card is recalled from a memory of a mobile device and used to complete a purchase transaction via the mobile device). Accordingly, for example, upon selection of one of sort options 1102 (e.g., Most used), a processor of a mobile device may recall usage statistics that may be associated with each virtual payment card stored within a memory of a mobile device and may display each virtual payment card within category 1106 onto GUI 1100 in accordance with such usage statistics (e.g., the top virtual payment card displayed within category 1106 may have the most usages of all virtual payment cards stored within a memory of the mobile device).
A mobile device may, for example, maintain other information associated with virtual payment cards of category 1106. Accordingly, for example, a mobile device may access network devices (e.g., issuer servers) associated with each virtual payment card stored within the mobile device. In so doing, for example, a mobile device may collect information (e.g., credit limit and credit available) associated with each virtual payment card stored within a memory of the mobile device and may display each virtual payment card on GUI 1100 in accordance with sort options 1102 (e.g., the top card displayed within category 1106 may have the highest credit limit or may have the most credit available).
Category 1108 may, for example, be associated with all virtual gift cards that may be stored within a memory of a mobile device (or remote server). Information associated with each virtual gift card may, for example, include a merchant identifier, a merchant type identifier, and an amount of credit available. Accordingly, for example, a user may select one of sort options 1104 (e.g., Most credit available) to display a list of virtual gift cards within category 1108 in a descending order, where the top virtual gift card of category 1108 may have the highest credit available.
A mobile device may, for example, be a locating device (e.g., a GPS) or may, for example, include location determination electronics.
Accordingly, for example, a mobile device may determine its own location and may determine whether its location corresponds with a location of a merchant's place of business that may be associated with a virtual gift card of category 1108. In so doing, for example, a mobile device may determine that its location is within a Walmart store and if, for example, sort options 1104 is selected to “Location”, then a processor of the mobile device may re-order the virtual gift cards of category 1106 such that a Walmart virtual gift card is displayed as the top card in the stack. Accordingly, for example, the Walmart virtual gift card may be conveniently located within GUI 1100 for selection by a user of a mobile device to use during a purchase transaction conducted between a contactless communication channel formed between the mobile device and a merchant terminal at the Walmart store.
Virtual cards may, for example, be autonomously sorted across categories depending upon a virtual card placement that may exist in a particular category. A virtual payment card may, for example, be selected to occupy a top card placement within category 1106. A virtual rewards card may, for example, be associated with the virtual payment card selected for top placement in category 1106. Accordingly, for example, the associated virtual rewards card may be selected for top placement within category 1108 based upon its association with the virtual payment card selected for top placement within category 1106. As per another example, a virtual identification card (e.g., a virtual driver's license card) may be selected for top placement within category 1110 based upon its general association with any virtual payment card selected for top placement within category 1106 or its general association with any virtual gift card selected for top placement within category 1108.
A mobile device may, for example, request electronic receipts to be delivered to the mobile device after purchase transactions are completed. Accordingly, for example, receipts may be delivered to the mobile device via an electronic delivery method (e.g., text messaging or email) and may be stored within a memory of the mobile device for future use. In so doing, for example, a user may select option 1406 to view a list of one or more receipts that may be associated with purchases conducted via the mobile device and virtual card 1402.
A mobile device may, for example, request electronic bank statements to be delivered to the mobile device at the end of each billing cycle of virtual card 1402. Alternately, for example, a mobile device may access a network entity (e.g., an issuer's server) to retrieve bank statement information that may be associated with virtual card 1402. Accordingly, for example, a user of a mobile device may review any and all bank statements associated with virtual card 1402 that a user's mobile device may have collected via its network access capabilities (e.g., a wireless access point or cellular network access infrastructure).
A mobile device may, for example, allow virtual card 1402 to be associated with one or more virtual cards stored within a memory of the mobile device (or remote server). For example, virtual card 1402 may be associated with one or more cards (e.g., a rewards card and a driver's license) and a user of a mobile device may view such associations using a GUI of the mobile device.
A mobile device may, for example, allow virtual card 1402 to be associated with one or more virtual cards that may be stored within a memory of another mobile device and/or may allow virtual card 1402 to be associated with one or more physical cards not stored within any mobile device. Virtual card 1402 may, for example, be one of many (e.g., two) cards issued against the same general account (e.g., a husband and wife joint charge account). Accordingly, for example, a mobile device may recognize that virtual card 1402 is one of a pair of cards associated with such a joint account and may provide information to the user of the mobile device about such associations.
Once mobile wallet 1502 is brought within a communication distance (e.g., within approximately 2 inches) of merchant terminal 1506, a contactless communication channel (e.g., RFID communication channel 1504) may be generated between mobile wallet 1502 and merchant terminal 1506. Payment information associated with a virtual payment card selected by a user of mobile wallet 1502 may, for example, be autonomously communicated by a processor of mobile wallet 1502 to merchant terminal 1506 via contactless communication channel 1504 once a presence of merchant terminal 1506 is detected by the processor of mobile wallet 1502.
Contactless communication channel 1504 may, for example, be a two-way communication channel. Accordingly, for example, merchant terminal 1506 may communicate information to mobile wallet 1502 via contactless communication channel 1504. In so doing, for example, merchant terminal 1506 may communicate a total sale amount to mobile wallet 1502 and may wait for a user of mobile wallet 1502 to acknowledge that the total sale amount is correct (e.g., a user of mobile wallet 1502 may press an acknowledgment key that causes mobile wallet 1502 to communicate a confirmation message to merchant terminal via contactless communication channel 1504). Further communication from merchant terminal 1506 may query mobile wallet 1502 as to whether a user of mobile wallet 1502 requires cash back.
Once a purchase transaction is completed, a user of mobile wallet 1502 may request a receipt to be delivered to mobile wallet 1502 via any one of a number of mediums. A user may, for example, request that a receipt be delivered to mobile wallet 1502 at a later time (e.g., receipt queued for delivery at a later time via text messaging or email). A user may, for example, request that a receipt be delivered to mobile wallet 1502 immediately. Accordingly, for example, an electronic receipt may be generated by merchant terminal 1506 and communicated to mobile wallet 1502 via contactless communication channel 1504.
An application executing on a mobile device (e.g., a receipt handler application associated with GUI 1500) may have its own address. Accordingly, for example, the receipt handler's address may be well known within a network (e.g., a payment network), such that a server (e.g., an email server associated with a merchant's payment server) may email an electronic receipt directly to the receipt handler application that may be running on the mobile device. In so doing, for example, one or more applications running on a mobile device may have well known addresses (e.g., email addresses and multimedia message addresses) associated with them, so that the applications may directly communicate with network entities to autonomously provide a user of the mobile device with up-to-date and valuable information.
Mobile wallet 1602 may, for example, allow a user of mobile wallet 1602 to annotate electronic receipt 1606 with a note that may be entered into alphanumeric entry box 1608. Mobile wallet 1602 may, for example, allow electronic receipt 1606 to be associated with a virtual card (e.g., virtual payment card VISA 3456 that was used to complete the purchase transaction) stored within a memory of mobile wallet 1602.
A mobile device may, for example, access a user's rewards account by accessing a network entity (e.g., an issuer's server) to determine information associated with the rewards account (e.g., number of rewards points earned). A mobile device may, for example, access the network entity on a regularly scheduled basis and store the retrieved rewards account information within a memory location of the mobile device. A mobile device may, for example, access the network entity only upon demand to retrieve rewards account information and may only display the retrieved rewards account information without storing the retrieved rewards account information.
GUI 1800 may, for example, allow a user to obtain further information that may be associated with virtual cards 1804 and/or 1806. A user may, for example, touch a display of a mobile device in the vicinity of virtual card 1804 to obtain other information (e.g., a rewards point balance) associated with virtual card 1804. Accordingly, for example, a user may obtain a rewards points total that may be associated with virtual card 1804 and may touch virtual card 1804 again to conduct a purchase transaction with rewards points that may be associated with virtual card 1804. In so doing, for example, a mobile device may, for example, establish a contactless communication channel (e.g., an RFID communication channel) with a merchant terminal and may communicate points information that may be associated with virtual card 1804 so that a purchase transaction may be completed using rewards points that may be associated with virtual card 1804.
GUI 1800 may, for example, provide other information to a user concerning virtual card 1806. For example, a processor of a mobile device may detect that an expiration date of virtual card 1806 is approaching. Accordingly, for example, a user may touch a display in the vicinity of virtual card 1806 to automatically renew the driver's license using the mobile device. In so doing, for example, a mobile device may contact a network entity (e.g., a driver's license renewal server) to order a renewal driver's license. The renewal driver's license may, for example, be delivered to the user as a physical card, in which case the user may upload information associated with the physical driver's license into the mobile device via a contactless communication channel formed between the physical driver's license and the mobile device. Alternately, for example, a mobile device may receive an electronic copy of a virtual driver's license and replace information associated with virtual card 1806 with the updated information received from a driver's license renewal server.
As per another example, powered card 1906 may include circuitry that may simulate a touch. Display 1904 may be touch-sensitive. Accordingly, for example, powered card 1906 may communicate data to mobile wallet 1902 by simulating a series of touches that may be sensed by display 1904 and processed by a processor of mobile wallet 1902 as data received from powered card 1906. Powered card 1906 may include light sensor 1910. Accordingly, for example, a processor of mobile wallet 1902 may generate a series of light pulses on a portion of display 1904 that may be detected by light sensor 1910 of powered card 1906 and processed by a processor of powered card 1906 as data communicated by mobile wallet 1902. In so doing, for example, data may be communicated by powered card 1906 via a series of simulated touches and data may be communicated by mobile wallet 1902 via a series of light pulses.
Information communicated by powered card 1906 to mobile wallet 1902 may, for example, include payment information (e.g., payment account number, expiration date, and cardholder name). Information communicated by powered card 1906 to mobile wallet 1902 may, for example, include other information relating to a configuration of powered card 1906 including, for example, whether or not a display exists and if so, at what location; whether or not a manual input interface (e.g., one or more buttons) exists and if so, at what location; and whether or not a light sensor exists and if so, at what location. Accordingly, for example, configuration information relating to powered card 1906 may be communicated to mobile wallet 1902, so that when a virtual card relating to powered card 1906 is generated and stored within mobile wallet 1902, the virtual card may employ all of the features that may be employed by its physical counterpart.
Information communicated by powered card 1906 may, for example, be encrypted. Decryption may, for example, be executed within mobile wallet 1902 so that information communicated by powered card 1906 may be stored within a memory of mobile wallet 1902 in a decrypted format. Alternately, for example, information communicated by powered card 1906 may be stored within a memory of mobile wallet 1902 in an encrypted format. Mobile wallet 1902 may, for example, authenticate itself to a network entity (e.g., an issuer server) such that each time encrypted information is recalled from a memory of mobile wallet 1902, a decryption key may be communicated by the network entity to mobile wallet 1902 for decryption purposes.
Accordingly, for example, manual input interfaces (e.g., virtual buttons 2006 through 2014) may have the same functionality on virtual card 2002 as they do on the physical counterpart to virtual card 2002. In so doing, for example, virtual buttons 2006 through 2014 may be displayed on portions of GUI 2000 that may be touch-sensitive, such that when virtual buttons 2006 through 2014 are touched, a processor of the mobile device may impart a functionality to the mobile device just as if the mobile device itself was the physical card (e.g., a PIN may be entered into virtual card 2002 via one or more buttons 2006-2014 to unlock virtual dynamic portion 2018 of virtual payment card number 2016).
A mobile device may, for example, provide a light-sensitive display, such that when virtual card 2002 is rendered onto the light-sensitive display, light sensor 2004 may exhibit the same functionality as its physical counterpart. Accordingly, for example, virtual card 2002 may be rendered so that light sensor 2004 exists on a light-sensitive portion of a display of a mobile device. A processor of the mobile device may, for example, detect light pulses sensed at light sensor 2004 as data communicated to virtual card 2002. In so doing, for example, virtual card 2002 may receive information that changes the functionality of virtual card 2002 (e.g., an expiration date of virtual payment card 2002 may be updated via light sensor 2004).
A mobile device may, for example, provide a display that may simulate touch. Accordingly, for example, virtual card 2002 may be rendered onto a display of a mobile device so that touch-simulating portion 2020 aligns with a portion of the display that may be capable of simulating touch. In so doing, for example, virtual card 2002 may communicate information to another device (e.g., another mobile device) when touch-simulating portion 2020 of GUI 2000 is pressed against another device (e.g., a touch-sensitive display of another mobile device) and simulates a series of touches that may be construed by a processor of the other device as data communicated to the other device.
Virtual display 2018 may, for example, display a dynamic portion of payment card number 2016 just as it would be displayed on the physical counterpart to virtual card 2002. For example, virtual card 2002 may be disabled for use when virtual display 2018 does not display a valid portion of virtual card number 2016. Upon entry of a password (e.g., a PIN may be entered by touching one or more buttons 2006-2014 that corresponds to the PIN), virtual card 2002 may be activated for use. Accordingly, for example, once a valid PIN is entered, virtual display 2018 may be populated with a remaining portion of virtual payment card number 2016 thereby activating virtual card 2002 for use. In so doing, for example, a mobile device that displays activated virtual card 2002 via GUI 2000 may communicate payment information (e.g., virtual payment card number 2016 and expiration date) to a device (e.g., a merchant terminal) via a contactless communication channel (e.g., an RFID communication channel) so that a purchase transaction may be completed between the mobile device and the merchant terminal.
A mobile device may, for example, establish a contactless communication channel (e.g., an RFID communication channel) with a merchant terminal to communicate payment information to the merchant terminal to complete a purchase transaction.
Accordingly, for example, a user may touch one of virtual buttons 2104-2108 just prior to placing the mobile device within a proximity to the merchant terminal. In so doing, for example, the mobile device may communicate one, two, and/or three tracks of magnetic stripe data to the merchant terminal and may include additional information (e.g., within a discretionary data field) to communicate a method of payment (e.g., credit, debit, or points) to the merchant terminal. Persons skilled in the art will appreciate that payment information may be communicated by a mobile device to a network entity (e.g., a payment server) via a wireless interface (e.g., a cellular interface) such that a method of payment (e.g., credit, debit, or points) may be communicated by the mobile device to the payment server to complete a remote purchase transaction.
GUI 2300 may, for example, provide credit offer options 2308 to a user of a mobile device. Accordingly, for example, a user may elect to accept a new credit offer and cancel a current virtual payment card with the same option. In so doing, for example, a mobile device may communicate with a network entity (e.g., an issuer of virtual payment card 2304) to cancel virtual payment card 2304 and may communicate with a network entity (e.g., an issuer for payment card offer 2306) to open the new payment account being offered.
Other options may be provided by GUI 2300. For example, a user may opt to accept the new credit offer, but keep virtual payment card 2304 as well. As per another example, a user may opt to accept the new credit offer, keep virtual payment card 2304, and transfer any balance that may be owing on virtual payment card 2304 to the new payment account now being offered.
Application 2400 may, for example, provide access to mobile wallet 2402 which may be another application running on a mobile device. Accordingly, for example, when application 2400 requires payment for a particular function performed by application 2400 (e.g., a user wishes to purchase goods from an Amazon website), application 2400 may launch mobile wallet 2402 to allow a user to select a method of payment from mobile wallet 2402. A user may browse through each virtual card of mobile wallet 2402 by touching a virtual card to display the virtual card. Once a user has verified that a particular virtual card is the virtual card to be used to complete a purchase transaction, the user may touch the virtual card twice again to authorize a mobile device to complete a purchase transaction using payment information associated with the selected virtual card.
As per another example, a user may preselect payment options, such that mobile application 2400 need not launch mobile wallet 2402 to obtain a payment authorization. Instead, for example, a user may pre-authorize one virtual payment card within mobile wallet 2402 to be used by any other application running on a mobile device for purchase transactions. In so doing, for example, a user may pre-authorize payment information to be autonomously retrieved from mobile wallet 2402 without involving user interaction to authorize application 2400 for the purchase transaction.
Process sequence 2520 may, for example, autonomously detect that a card is in a touching or a proximity relationship to a mobile device (e.g., as in step 2521). In step 2522, a contactless communication channel (e.g., an RF, capacitive, audible, visible, electromagnetic, or magnetic communication channel) may be generated between a card and a mobile device to communicate information from the card to the mobile device. In step 2523, information associated with each physical card presented to the mobile device may be stored within the mobile device for future use.
Step 2531 of sequence 2630 may include presenting a card to a mobile device. A card may, for example, be a powered card or a non-powered card. In steps 2532 and 2533, a contactless communication channel may be established between a card and a mobile device and information may be exchanged between the card and the mobile device.
A card may, for example, include a near-field communication device (e.g., an RFID) that may communicate with a contactless communication device of a mobile device to form a two-way communication channel between the card and the mobile device. A card may, for example, include circuitry to simulate touch (e.g., a capacitance change) in order to form a contactless communication channel with a mobile device.
Accordingly, for example, a card may be pressed against a touch-sensitive display of a mobile device and information may be communicated by the card to the mobile device through a series of card-simulated touches that may be detected by the touch-sensitive display of the mobile device.
A card may, for example, include a light sensor to form a contactless communication channel with a mobile device. Accordingly, for example, a card may be pressed against a display of a mobile device and information may be communicated from the mobile device to the card through a series of light pulses generated by the display of the mobile device. A frequency, pulse width, and/or a pulse intensity of light pulses may, for example, be detected by a processor of a card as data communicated by a mobile device.
A card may, for example, include a light source (e.g., an LED) to form a contactless communication channel. Accordingly, for example, a card may emit varying light pulses from an LED that may be detected by a motion-capture device (e.g., a camera) of a mobile device as data communicated by the card. A card may, for example, include sound emission capabilities that may be detected by a microphone of a mobile device as data communicated by the card through a contactless communication channel. A mobile device may, for example, include sound emission capabilities that may be detected by a microphone of a card as data communicated by the mobile device through a contactless communication channel.
Step 2541 of sequence 2540 may include arranging information contained within a memory of a mobile device and/or a remote server and rendering the information on a display of a mobile device. The rendered information may, for example, be virtual cards that are representative of physical card counterparts previously presented to the mobile device for upload.
The virtual cards may, for example, be arranged according to category (e.g., payment cards, gift cards and identification cards). Within each category, virtual cards may be sorted according to any sort preference. For example, payment cards may be sorted in an order of most frequently used to least frequently used, in order of most available credit to least available credit, or in order of highest credit limit to lowest credit limit. Other cards (e.g., merchant gift cards) may be sorted in accordance with a user's location. For example, a mobile device may determine a location of its user and may sort virtual cards in response to the determined location (e.g., a virtual Walmart gift card may be displayed at the top of a gift card list based upon a user's location within a Walmart store).
Virtual cards displayed by a GUI of a mobile device may, for example, be selected for use (e.g., as in step 2542). A user may, for example, touch a virtual card among several virtual cards displayed by a mobile device to view information related to the touched virtual card. If desired for use, the touched virtual card may be touched twice again and activated for use (e.g., as in step 2543). An activated virtual card may, for example, be used to complete a purchase transaction via the mobile device. An activated virtual card may, for example, be deleted from a memory of the mobile device. Documents associated with an activated virtual card, such as purchase transaction receipts and bank statements, may be viewed from a display of a mobile device. Virtual cards that may be associated with an activated virtual card may be viewed from a display of a mobile device and activated themselves to perform other functions (e.g., an activated virtual payment card may be associated with a virtual rewards card, where the virtual rewards card may be activated to obtain and view the total number of rewards points that may be associated with the virtual rewards card).
Step 2551 of sequence 2550 may include running an application on a mobile device. Such an application may be any executable application that may require purchase transactions to be completed while the application executes. As per one example, a user booking airline tickets using his or her mobile device may select their itinerary and may book their itinerary through a purchase transaction conducted by the mobile device. Accordingly, for example, the mobile application may request access to a mobile wallet application also running on the mobile device (e.g., as in step 2552), a user may grant access to the mobile wallet application (e.g., as in step 2553) by selecting a virtual payment card from within the mobile wallet and may authorize a purchase transaction to be conducted by the mobile application using the authorized virtual payment card. As per another example, a mobile application may autonomously request access to a mobile wallet application (e.g., as in step 2552) that has been pre-authorized by a user of the mobile device (e.g., as in step 2553) such that the mobile application may autonomously conduct the purchase transaction without any further involvement with the user.
Persons skilled in the art will appreciate that the present invention is not limited to only the embodiments described. Instead, the present invention more generally involves dynamic information and the exchange thereof. Persons skilled in the art will also appreciate that the apparatus of the present invention may be implemented in other ways than those described herein. All such modifications are within the scope of the present invention, which is limited only by the claims that follow.
This application claims the benefit of U.S. Provisional Patent Application Nos. 61/484,547, titled “SYSTEMS AND DEVICES FOR MOBILE PAYMENT ACCEPTANCE,” filed May 10, 2011, 61/484,566, titled “SYSTEMS AND METHODS FOR A MOBILE ELECTRONIC WALLET,” filed May 10, 2011, 61/484,576, titled “SYSTEMS AND METHODS FOR MOBILE AUTHORIZATIONS,” filed May 10, 2011, and 61/484,588, titled “SYSTEMS AND METHODS FOR CONTACTLESS COMMUNICATION MECHANISMS FOR CARDS AND MOBILE DEVICES,” filed May 10, 2011 all of which are hereby incorporated by reference herein in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4353064 | Stamm | Oct 1982 | A |
| 4394654 | Hofmann-Cerfontaine | Jul 1983 | A |
| 4614861 | Pavlov et al. | Sep 1986 | A |
| 4667087 | Quintana | May 1987 | A |
| 4701601 | Francini et al. | Oct 1987 | A |
| 4720860 | Weiss | Jan 1988 | A |
| 4786791 | Hodama | Nov 1988 | A |
| 4791283 | Burkhardt | Dec 1988 | A |
| 4797542 | Hara | Jan 1989 | A |
| 5038251 | Sugiyama et al. | Aug 1991 | A |
| 5168520 | Weiss | Dec 1992 | A |
| 5237614 | Weiss | Aug 1993 | A |
| 5276311 | Hennige | Jan 1994 | A |
| 5347580 | Molva et al. | Sep 1994 | A |
| 5361062 | Weiss et al. | Nov 1994 | A |
| 5412199 | Finkelstein et al. | May 1995 | A |
| 5434398 | Goldberg | Jul 1995 | A |
| 5434405 | Finkelstein et al. | Jul 1995 | A |
| 5478994 | Rahman | Dec 1995 | A |
| 5479512 | Weiss | Dec 1995 | A |
| 5484997 | Haynes | Jan 1996 | A |
| 5485519 | Weiss | Jan 1996 | A |
| 5585787 | Wallerstein | Dec 1996 | A |
| 5591949 | Bernstein | Jan 1997 | A |
| 5608203 | Finkelstein et al. | Mar 1997 | A |
| 5623552 | Lane | Apr 1997 | A |
| 5657388 | Weiss | Aug 1997 | A |
| 5748737 | Daggar | May 1998 | A |
| 5834747 | Cooper | Nov 1998 | A |
| 5834756 | Gutman et al. | Nov 1998 | A |
| 5856661 | Finkelstein et al. | Jan 1999 | A |
| 5864623 | Messina et al. | Jan 1999 | A |
| 5907142 | Kelsey | May 1999 | A |
| 5913203 | Wong et al. | Jun 1999 | A |
| 5937394 | Wong et al. | Aug 1999 | A |
| 5955021 | Tiffany, III | Sep 1999 | A |
| 5956699 | Wong et al. | Sep 1999 | A |
| 6025054 | Tiffany, III | Feb 2000 | A |
| 6045043 | Bashan et al. | Apr 2000 | A |
| 6076163 | Hoffstein et al. | Jun 2000 | A |
| 6085320 | Kaliski | Jul 2000 | A |
| 6095416 | Grant et al. | Aug 2000 | A |
| 6130621 | Weiss | Oct 2000 | A |
| 6145079 | Mitty et al. | Nov 2000 | A |
| 6157920 | Jakobsson et al. | Dec 2000 | A |
| 6161181 | Haynes, III et al. | Dec 2000 | A |
| 6176430 | Finkelstein et al. | Jan 2001 | B1 |
| 6182894 | Hackett et al. | Feb 2001 | B1 |
| 6189098 | Kaliski | Feb 2001 | B1 |
| 6199052 | Mitty et al. | Mar 2001 | B1 |
| 6206293 | Gutman et al. | Mar 2001 | B1 |
| 6240184 | Huynh et al. | May 2001 | B1 |
| 6241153 | Tiffany, III | Jun 2001 | B1 |
| 6256873 | Tiffany, III | Jul 2001 | B1 |
| 6269163 | Rivest et al. | Jul 2001 | B1 |
| 6286022 | Kaliski et al. | Sep 2001 | B1 |
| 6308890 | Cooper | Oct 2001 | B1 |
| 6313724 | Osterweil | Nov 2001 | B1 |
| 6353811 | Weissman | Mar 2002 | B1 |
| 6389442 | Yin et al. | May 2002 | B1 |
| 6393447 | Jakobsson et al. | May 2002 | B1 |
| 6411715 | Liskov et al. | Jun 2002 | B1 |
| 6446052 | Juels | Sep 2002 | B1 |
| 6460141 | Olden | Oct 2002 | B1 |
| 6592044 | Wong et al. | Jul 2003 | B1 |
| 6607127 | Wong | Aug 2003 | B2 |
| 6609654 | Anderson et al. | Aug 2003 | B1 |
| 6631849 | Blossom | Oct 2003 | B2 |
| 6655585 | Shinn | Dec 2003 | B2 |
| 6681988 | Stack et al. | Jan 2004 | B2 |
| 6705520 | Pitroda et al. | Mar 2004 | B1 |
| 6755341 | Wong et al. | Jun 2004 | B1 |
| 6764005 | Cooper | Jul 2004 | B2 |
| 6769618 | Finkelstein | Aug 2004 | B1 |
| 6805288 | Routhenstein et al. | Oct 2004 | B2 |
| 6811082 | Wong | Nov 2004 | B2 |
| 6813354 | Jakobsson et al. | Nov 2004 | B1 |
| 6817532 | Finkelstein | Nov 2004 | B2 |
| 6873974 | Schutzer | Mar 2005 | B1 |
| 6902116 | Finkelstein | Jun 2005 | B2 |
| 6970070 | Juels et al. | Nov 2005 | B2 |
| 6980969 | Tuchler et al. | Dec 2005 | B1 |
| 6985583 | Brainard et al. | Jan 2006 | B1 |
| 6991155 | Burchette, Jr. | Jan 2006 | B2 |
| 7013030 | Wong et al. | Mar 2006 | B2 |
| 7035443 | Wong | Apr 2006 | B2 |
| 7039223 | Wong | May 2006 | B2 |
| 7044394 | Brown | May 2006 | B2 |
| 7051929 | Li | May 2006 | B2 |
| 7083094 | Cooper | Aug 2006 | B2 |
| 7100049 | Gasparini et al. | Aug 2006 | B2 |
| 7100821 | Rasti | Sep 2006 | B2 |
| 7111172 | Duane et al. | Sep 2006 | B1 |
| 7114652 | Moullette et al. | Oct 2006 | B2 |
| 7136514 | Wong | Nov 2006 | B1 |
| 7140550 | Ramachandran | Nov 2006 | B2 |
| 7163153 | Blossom | Jan 2007 | B2 |
| 7195154 | Routhenstein | Mar 2007 | B2 |
| 7197639 | Juels et al. | Mar 2007 | B1 |
| 7219368 | Juels et al. | May 2007 | B2 |
| 7225537 | Reed | Jun 2007 | B2 |
| 7225994 | Finkelstein | Jun 2007 | B2 |
| 7246752 | Brown | Jul 2007 | B2 |
| 7298243 | Juels et al. | Nov 2007 | B2 |
| 7334732 | Cooper | Feb 2008 | B2 |
| 7337326 | Palmer et al. | Feb 2008 | B2 |
| 7346775 | Gasparini et al. | Mar 2008 | B2 |
| 7356696 | Jakobsson et al. | Apr 2008 | B1 |
| 7357319 | Lin et al. | Apr 2008 | B1 |
| 7359507 | Kaliski | Apr 2008 | B2 |
| 7360688 | Harris | Apr 2008 | B1 |
| 7363494 | Brainard et al. | Apr 2008 | B2 |
| 7380710 | Brown | Jun 2008 | B2 |
| 7398253 | Pinnell | Jul 2008 | B1 |
| 7404087 | Teunen | Jul 2008 | B2 |
| 7424570 | D'Albore et al. | Sep 2008 | B2 |
| 7427033 | Roskind | Sep 2008 | B1 |
| 7454349 | Teunen et al. | Nov 2008 | B2 |
| 7461250 | Duane et al. | Dec 2008 | B1 |
| 7461399 | Juels et al. | Dec 2008 | B2 |
| 7472093 | Juels | Dec 2008 | B2 |
| 7472829 | Brown | Jan 2009 | B2 |
| 7483858 | Foran et al. | Jan 2009 | B2 |
| 7494055 | Fernandes et al. | Feb 2009 | B2 |
| 7502467 | Brainard et al. | Mar 2009 | B2 |
| 7502933 | Jakobsson et al. | Mar 2009 | B2 |
| 7503485 | Routhenstein | Mar 2009 | B1 |
| 7516492 | Nisbet et al. | Apr 2009 | B1 |
| 7523301 | Nisbet et al. | Apr 2009 | B2 |
| 7530495 | Cooper | May 2009 | B2 |
| 7532104 | Juels | May 2009 | B2 |
| 7543739 | Brown et al. | Jun 2009 | B2 |
| 7559464 | Routhenstein | Jul 2009 | B2 |
| 7562221 | Nystrom et al. | Jul 2009 | B2 |
| 7562222 | Gasparini et al. | Jul 2009 | B2 |
| 7580898 | Brown et al. | Aug 2009 | B2 |
| 7584153 | Brown et al. | Sep 2009 | B2 |
| 7591426 | Osterweil et al. | Sep 2009 | B2 |
| 7591427 | Osterweil | Sep 2009 | B2 |
| 7602904 | Juels et al. | Oct 2009 | B2 |
| 7631804 | Brown | Dec 2009 | B2 |
| 7639537 | Sepe et al. | Dec 2009 | B2 |
| 7641124 | Brown et al. | Jan 2010 | B2 |
| 7660902 | Graham et al. | Feb 2010 | B2 |
| 7784687 | Mullen et al. | Aug 2010 | B2 |
| 7793851 | Mullen | Sep 2010 | B2 |
| 7828207 | Cooper | Nov 2010 | B2 |
| 7828220 | Mullen | Nov 2010 | B2 |
| 7931195 | Mullen | Apr 2011 | B2 |
| 7954705 | Mullen | Jun 2011 | B2 |
| D643063 | Mullen et al. | Aug 2011 | S |
| 8011577 | Mullen et al. | Sep 2011 | B2 |
| 8020775 | Mullen et al. | Sep 2011 | B2 |
| 8066191 | Cloutier et al. | Nov 2011 | B1 |
| D651237 | Mullen et al. | Dec 2011 | S |
| D651238 | Mullen et al. | Dec 2011 | S |
| 8074877 | Mullen et al. | Dec 2011 | B2 |
| D651644 | Mullen et al. | Jan 2012 | S |
| D652075 | Mullen et al. | Jan 2012 | S |
| D652076 | Mullen et al. | Jan 2012 | S |
| D652448 | Mullen et al. | Jan 2012 | S |
| D652449 | Mullen et al. | Jan 2012 | S |
| D652450 | Mullen et al. | Jan 2012 | S |
| D652867 | Mullen et al. | Jan 2012 | S |
| D653288 | Mullen et al. | Jan 2012 | S |
| 8172148 | Cloutier et al. | May 2012 | B1 |
| D665022 | Mullen et al. | Aug 2012 | S |
| D665447 | Mullen et al. | Aug 2012 | S |
| D666241 | Mullen et al. | Aug 2012 | S |
| 8282007 | Cloutier et al. | Oct 2012 | B1 |
| 8286876 | Mullen et al. | Oct 2012 | B2 |
| D670759 | Mullen et al. | Nov 2012 | S |
| 8302872 | Mullen | Nov 2012 | B2 |
| D672389 | Mullen et al. | Dec 2012 | S |
| 8322623 | Mullen et al. | Dec 2012 | B1 |
| D674013 | Mullen et al. | Jan 2013 | S |
| 8348172 | Cloutier et al. | Jan 2013 | B1 |
| 8382000 | Mullen et al. | Feb 2013 | B2 |
| 8393545 | Mullen et al. | Mar 2013 | B1 |
| 8393546 | Yen et al. | Mar 2013 | B1 |
| 8413892 | Mullen et al. | Apr 2013 | B2 |
| 8424773 | Mullen et al. | Apr 2013 | B2 |
| 8459548 | Mullen et al. | Jun 2013 | B2 |
| D687094 | Mullen et al. | Jul 2013 | S |
| 8485437 | Mullen et al. | Jul 2013 | B2 |
| 8485446 | Mullen et al. | Jul 2013 | B1 |
| 8511574 | Yen et al. | Aug 2013 | B1 |
| 8517276 | Mullen et al. | Aug 2013 | B2 |
| 8523059 | Mullen et al. | Sep 2013 | B1 |
| 8561894 | Mullen et al. | Oct 2013 | B1 |
| 8567679 | Mullen et al. | Oct 2013 | B1 |
| 8573503 | Cloutier et al. | Nov 2013 | B1 |
| 8579203 | Lambeth et al. | Nov 2013 | B1 |
| 8590796 | Cloutier et al. | Nov 2013 | B1 |
| 8602312 | Cloutier et al. | Dec 2013 | B2 |
| 8608083 | Mullen et al. | Dec 2013 | B2 |
| 8622309 | Mullen et al. | Jan 2014 | B1 |
| 8668143 | Mullen et al. | Mar 2014 | B2 |
| 8727219 | Mullen | May 2014 | B1 |
| 8733638 | Mullen et al. | May 2014 | B2 |
| 8746579 | Cloutier et al. | Jun 2014 | B1 |
| 8757483 | Mullen et al. | Jun 2014 | B1 |
| 8757499 | Cloutier et al. | Jun 2014 | B2 |
| 8814050 | Mullen et al. | Aug 2014 | B1 |
| 8875999 | Mullen et al. | Nov 2014 | B2 |
| 8881989 | Mullen et al. | Nov 2014 | B2 |
| 8931703 | Mullen et al. | Jan 2015 | B1 |
| 8944333 | Mullen et al. | Feb 2015 | B1 |
| 8973824 | Mullen et al. | Mar 2015 | B2 |
| 9004368 | Mullen et al. | Apr 2015 | B2 |
| 9010630 | Mullen et al. | Apr 2015 | B2 |
| 9053398 | Cloutier | Jun 2015 | B1 |
| 9064255 | Mullen et al. | Jun 2015 | B1 |
| 9292843 | Mullen et al. | Mar 2016 | B1 |
| 9306666 | Zhang et al. | Apr 2016 | B1 |
| 9329619 | Cloutier | May 2016 | B1 |
| 9361569 | Mullen et al. | Jun 2016 | B2 |
| 9373069 | Cloutier et al. | Jun 2016 | B2 |
| 9384438 | Mullen et al. | Jul 2016 | B2 |
| 9547816 | Mullen et al. | Jan 2017 | B2 |
| 9639796 | Mullen et al. | May 2017 | B2 |
| 9646240 | Mullen et al. | May 2017 | B1 |
| 9652436 | Yen et al. | May 2017 | B1 |
| 9684861 | Mullen et al. | Jun 2017 | B2 |
| D792511 | Mullen et al. | Jul 2017 | S |
| D792512 | Mullen et al. | Jul 2017 | S |
| D792513 | Mullen et al. | Jul 2017 | S |
| 9697454 | Mullen et al. | Jul 2017 | B2 |
| 9704088 | Mullen et al. | Jul 2017 | B2 |
| 9704089 | Mullen et al. | Jul 2017 | B2 |
| 9721201 | Mullen et al. | Aug 2017 | B1 |
| 9727813 | Mullen et al. | Aug 2017 | B2 |
| 9805297 | Mullen et al. | Oct 2017 | B2 |
| 9818125 | Mullen et al. | Nov 2017 | B2 |
| 9836680 | Cloutier | Dec 2017 | B1 |
| 9852368 | Yen et al. | Dec 2017 | B1 |
| 9875437 | Cloutier et al. | Jan 2018 | B2 |
| 9928456 | Cloutier et al. | Mar 2018 | B1 |
| 9953255 | Yen et al. | Apr 2018 | B1 |
| 10022884 | Cloutier | Jul 2018 | B1 |
| 10032100 | Mullen et al. | Jul 2018 | B2 |
| 10055614 | Cloutier et al. | Aug 2018 | B1 |
| 10095970 | Mullen | Oct 2018 | B1 |
| 10095974 | Mullen et al. | Oct 2018 | B1 |
| 10169692 | Mullen et al. | Jan 2019 | B2 |
| 10176419 | Cloutier et al. | Jan 2019 | B1 |
| 10176423 | Mullen et al. | Jan 2019 | B1 |
| 10181097 | Mullen et al. | Jan 2019 | B1 |
| 10198687 | Mullen et al. | Feb 2019 | B2 |
| 10223631 | Mullen et al. | Mar 2019 | B2 |
| 10255545 | Mullen et al. | Apr 2019 | B2 |
| 10325199 | Mullen et al. | Jun 2019 | B2 |
| 10430704 | Mullen et al. | Oct 2019 | B2 |
| 10467521 | Mullen et al. | Nov 2019 | B2 |
| 10482363 | Cloutier et al. | Nov 2019 | B1 |
| 10496918 | Mullen et al. | Dec 2019 | B2 |
| 10504105 | Mullen et al. | Dec 2019 | B2 |
| 10579920 | Mullen et al. | Mar 2020 | B2 |
| 10693263 | Mullen et al. | Jun 2020 | B1 |
| 10948964 | Cloutier | Mar 2021 | B1 |
| 10997489 | Mullen et al. | May 2021 | B2 |
| 11062195 | Mullen | Jul 2021 | B2 |
| 11238329 | Mullen et al. | Feb 2022 | B2 |
| 20010034702 | Mockett et al. | Oct 2001 | A1 |
| 20010047335 | Arndt et al. | Nov 2001 | A1 |
| 20010049635 | Chung | Dec 2001 | A1 |
| 20020059114 | Cockrill et al. | May 2002 | A1 |
| 20020082989 | Fife et al. | Jun 2002 | A1 |
| 20020096570 | Wong et al. | Jul 2002 | A1 |
| 20020120583 | Keresman, III et al. | Aug 2002 | A1 |
| 20030034388 | Routhenstein et al. | Feb 2003 | A1 |
| 20030052168 | Wong | Mar 2003 | A1 |
| 20030057278 | Wong | Mar 2003 | A1 |
| 20030116635 | Taban | Jun 2003 | A1 |
| 20030144956 | Yu, Jr. | Jul 2003 | A1 |
| 20030152253 | Wong | Aug 2003 | A1 |
| 20030163287 | Vock et al. | Aug 2003 | A1 |
| 20030173409 | Vogt et al. | Sep 2003 | A1 |
| 20030179909 | Wong et al. | Sep 2003 | A1 |
| 20030179910 | Wong | Sep 2003 | A1 |
| 20030226899 | Finkelstein | Dec 2003 | A1 |
| 20040035942 | Silverman | Feb 2004 | A1 |
| 20040054574 | Kaufman et al. | Mar 2004 | A1 |
| 20040133787 | Doughty | Jul 2004 | A1 |
| 20040162732 | Rahim et al. | Aug 2004 | A1 |
| 20040172535 | Jakobsson | Sep 2004 | A1 |
| 20040177045 | Brown | Sep 2004 | A1 |
| 20050043997 | Sohata et al. | Feb 2005 | A1 |
| 20050080747 | Anderson et al. | Apr 2005 | A1 |
| 20050086160 | Wong et al. | Apr 2005 | A1 |
| 20050086177 | Anderson et al. | Apr 2005 | A1 |
| 20050116026 | Burger et al. | Jun 2005 | A1 |
| 20050119940 | Concilio et al. | Jun 2005 | A1 |
| 20050154643 | Doan et al. | Jul 2005 | A1 |
| 20050228959 | D'Albore et al. | Oct 2005 | A1 |
| 20060000900 | Fernandes et al. | Jan 2006 | A1 |
| 20060037073 | Juels et al. | Feb 2006 | A1 |
| 20060041759 | Kaliski et al. | Feb 2006 | A1 |
| 20060085328 | Cohen et al. | Apr 2006 | A1 |
| 20060091223 | Zellner | May 2006 | A1 |
| 20060161435 | Atef et al. | Jul 2006 | A1 |
| 20060163353 | Moulette et al. | Jul 2006 | A1 |
| 20060174104 | Crichton et al. | Aug 2006 | A1 |
| 20060196931 | Holtmanns et al. | Sep 2006 | A1 |
| 20060256961 | Brainard et al. | Nov 2006 | A1 |
| 20070034700 | Poidomani et al. | Feb 2007 | A1 |
| 20070114274 | Gibbs et al. | May 2007 | A1 |
| 20070124321 | Szydlo | May 2007 | A1 |
| 20070152070 | D'Albore | Jul 2007 | A1 |
| 20070152072 | Frallicciardi et al. | Jul 2007 | A1 |
| 20070153487 | Frallicciardi et al. | Jul 2007 | A1 |
| 20070174614 | Duane et al. | Jul 2007 | A1 |
| 20070241183 | Brown et al. | Oct 2007 | A1 |
| 20070241201 | Brown et al. | Oct 2007 | A1 |
| 20070256123 | Duane et al. | Nov 2007 | A1 |
| 20070192249 | Biffle et al. | Dec 2007 | A1 |
| 20070291753 | Romano | Dec 2007 | A1 |
| 20080005510 | Sepe et al. | Jan 2008 | A1 |
| 20080008315 | Fontana et al. | Jan 2008 | A1 |
| 20080008322 | Fontana et al. | Jan 2008 | A1 |
| 20080010675 | Massascusa et al. | Jan 2008 | A1 |
| 20080016351 | Fontana et al. | Jan 2008 | A1 |
| 20080019507 | Fontana et al. | Jan 2008 | A1 |
| 20080028447 | O'Malley et al. | Jan 2008 | A1 |
| 20080029607 | Mullen | Feb 2008 | A1 |
| 20080035738 | Mullen | Feb 2008 | A1 |
| 20080040271 | Hammad et al. | Feb 2008 | A1 |
| 20080040276 | Hammad et al. | Feb 2008 | A1 |
| 20080054068 | Mullen | Mar 2008 | A1 |
| 20080054079 | Mullen | Mar 2008 | A1 |
| 20080054081 | Mullen | Mar 2008 | A1 |
| 20080058016 | Di Maggio et al. | Mar 2008 | A1 |
| 20080059379 | Ramaci et al. | Mar 2008 | A1 |
| 20080065555 | Mullen | Mar 2008 | A1 |
| 20080096326 | Reed | Apr 2008 | A1 |
| 20080126398 | Cimino | May 2008 | A1 |
| 20080128515 | Di Iorio | Jun 2008 | A1 |
| 20080148394 | Poidomani et al. | Jun 2008 | A1 |
| 20080201264 | Brown et al. | Aug 2008 | A1 |
| 20080209550 | Di Iorio | Aug 2008 | A1 |
| 20080288699 | Chichierchia | Nov 2008 | A1 |
| 20080294930 | Varone et al. | Nov 2008 | A1 |
| 20080302869 | Mullen | Dec 2008 | A1 |
| 20080302876 | Mullen | Dec 2008 | A1 |
| 20080302877 | Musella et al. | Dec 2008 | A1 |
| 20090013122 | Sepe et al. | Jan 2009 | A1 |
| 20090036147 | Romano | Feb 2009 | A1 |
| 20090046522 | Sepe et al. | Feb 2009 | A1 |
| 20090108064 | Fernandes et al. | Apr 2009 | A1 |
| 20090143104 | Loh | Jun 2009 | A1 |
| 20090150295 | Hatch et al. | Jun 2009 | A1 |
| 20090152365 | Li et al. | Jun 2009 | A1 |
| 20090159663 | Mullen et al. | Jun 2009 | A1 |
| 20090159667 | Mullen et al. | Jun 2009 | A1 |
| 20090159668 | Mullen et al. | Jun 2009 | A1 |
| 20090159669 | Mullen et al. | Jun 2009 | A1 |
| 20090159670 | Mullen et al. | Jun 2009 | A1 |
| 20090159671 | Mullen et al. | Jun 2009 | A1 |
| 20090159672 | Mullen et al. | Jun 2009 | A1 |
| 20090159673 | Mullen et al. | Jun 2009 | A1 |
| 20090159680 | Mullen et al. | Jun 2009 | A1 |
| 20090159681 | Mullen et al. | Jun 2009 | A1 |
| 20090159682 | Mullen et al. | Jun 2009 | A1 |
| 20090159688 | Mullen et al. | Jun 2009 | A1 |
| 20090159689 | Mullen et al. | Jun 2009 | A1 |
| 20090159690 | Mullen et al. | Jun 2009 | A1 |
| 20090159696 | Mullen | Jun 2009 | A1 |
| 20090159697 | Mullen et al. | Jun 2009 | A1 |
| 20090159698 | Mullen et al. | Jun 2009 | A1 |
| 20090159699 | Mullen et al. | Jun 2009 | A1 |
| 20090159700 | Mullen | Jun 2009 | A1 |
| 20090159701 | Mullen et al. | Jun 2009 | A1 |
| 20090159702 | Mullen | Jun 2009 | A1 |
| 20090159703 | Mullen et al. | Jun 2009 | A1 |
| 20090159704 | Mullen et al. | Jun 2009 | A1 |
| 20090159705 | Mullen et al. | Jun 2009 | A1 |
| 20090159706 | Mullen et al. | Jun 2009 | A1 |
| 20090159707 | Mullen et al. | Jun 2009 | A1 |
| 20090159708 | Mullen et al. | Jun 2009 | A1 |
| 20090159709 | Mullen | Jun 2009 | A1 |
| 20090159710 | Mullen et al. | Jun 2009 | A1 |
| 20090159711 | Mullen et al. | Jun 2009 | A1 |
| 20090159712 | Mullen et al. | Jun 2009 | A1 |
| 20090159713 | Mullen et al. | Jun 2009 | A1 |
| 20090160617 | Mullen et al. | Jun 2009 | A1 |
| 20090170432 | Lortz | Jul 2009 | A1 |
| 20090170559 | Phillips | Jul 2009 | A1 |
| 20090191811 | Griffin et al. | Jul 2009 | A1 |
| 20090210308 | Toomer et al. | Aug 2009 | A1 |
| 20090222383 | Tato et al. | Sep 2009 | A1 |
| 20090242648 | Di Sirio et al. | Oct 2009 | A1 |
| 20090244858 | Di Sirio et al. | Oct 2009 | A1 |
| 20090253460 | Varone et al. | Oct 2009 | A1 |
| 20090255996 | Brown et al. | Oct 2009 | A1 |
| 20090290704 | Cimino | Nov 2009 | A1 |
| 20090303885 | Longo | Dec 2009 | A1 |
| 20090308921 | Mullen | Dec 2009 | A1 |
| 20100020043 | Park et al. | Jan 2010 | A1 |
| 20100023449 | Skowronek et al. | Jan 2010 | A1 |
| 20100078472 | Lin et al. | Apr 2010 | A1 |
| 20100082445 | Hodge | Apr 2010 | A1 |
| 20100153269 | McCabe | Jun 2010 | A1 |
| 20100260388 | Garrett | Oct 2010 | A1 |
| 20100304670 | Shuo | Dec 2010 | A1 |
| 20100315678 | Smires et al. | Dec 2010 | A1 |
| 20110028184 | Cooper | Feb 2011 | A1 |
| 20110066550 | Clinton et al. | Mar 2011 | A1 |
| 20110140841 | Bona | Jun 2011 | A1 |
| 20110272465 | Mullen et al. | Nov 2011 | A1 |
| 20110272466 | Mullen et al. | Nov 2011 | A1 |
| 20110272467 | Mullen et al. | Nov 2011 | A1 |
| 20110272471 | Mullen | Nov 2011 | A1 |
| 20110272472 | Mullen | Nov 2011 | A1 |
| 20110272473 | Mullen et al. | Nov 2011 | A1 |
| 20110272474 | Mullen et al. | Nov 2011 | A1 |
| 20110272475 | Mullen et al. | Nov 2011 | A1 |
| 20110272476 | Mullen et al. | Nov 2011 | A1 |
| 20110272477 | Mullen et al. | Nov 2011 | A1 |
| 20110272478 | Mullen | Nov 2011 | A1 |
| 20110272479 | Mullen | Nov 2011 | A1 |
| 20110272480 | Mullen et al. | Nov 2011 | A1 |
| 20110272481 | Mullen et al. | Nov 2011 | A1 |
| 20110272482 | Mullen et al. | Nov 2011 | A1 |
| 20110272483 | Mullen et al. | Nov 2011 | A1 |
| 20110272484 | Mullen et al. | Nov 2011 | A1 |
| 20110276380 | Mullen et al. | Nov 2011 | A1 |
| 20110276381 | Mullen et al. | Nov 2011 | A1 |
| 20110276416 | Mullen et al. | Nov 2011 | A1 |
| 20110276424 | Mullen | Nov 2011 | A1 |
| 20110276425 | Mullen | Nov 2011 | A1 |
| 20110276436 | Mullen et al. | Nov 2011 | A1 |
| 20110276437 | Mullen et al. | Nov 2011 | A1 |
| 20110278364 | Mullen et al. | Nov 2011 | A1 |
| 20110282753 | Mullen et al. | Nov 2011 | A1 |
| 20110284632 | Mullen et al. | Nov 2011 | A1 |
| 20110284640 | Mullen et al. | Nov 2011 | A1 |
| 20120028702 | Mullen et al. | Feb 2012 | A1 |
| 20120037709 | Cloutier et al. | Feb 2012 | A1 |
| 20120191612 | Spodak et al. | Jul 2012 | A1 |
| 20120197708 | Mullen et al. | Aug 2012 | A1 |
| 20120209744 | Mullen et al. | Aug 2012 | A1 |
| 20120254037 | Mullen | Oct 2012 | A1 |
| 20120286037 | Mullen et al. | Nov 2012 | A1 |
| 20120286928 | Mullen et al. | Nov 2012 | A1 |
| 20120286936 | Mullen et al. | Nov 2012 | A1 |
| 20120318871 | Mullen et al. | Dec 2012 | A1 |
| 20120326013 | Cloutier et al. | Dec 2012 | A1 |
| 20130020396 | Mullen et al. | Jan 2013 | A1 |
| 20130221092 | Kushevsky | Aug 2013 | A1 |
| 20130282573 | Mullen et al. | Oct 2013 | A1 |
| 20130282575 | Mullen et al. | Oct 2013 | A1 |
| 20140054384 | Cloutier et al. | Feb 2014 | A1 |
| 20150186766 | Mullen et al. | Jul 2015 | A1 |
| 20160162713 | Cloutier et al. | Jun 2016 | A1 |
| 20160180209 | Mullen et al. | Jun 2016 | A1 |
| 20160239735 | Mullen et al. | Aug 2016 | A1 |
| 20160283837 | Mullen et al. | Sep 2016 | A1 |
| 20160307085 | Mullen et al. | Oct 2016 | A1 |
| 20160335529 | Mullen et al. | Nov 2016 | A1 |
| 20160342876 | Mullen et al. | Nov 2016 | A1 |
| 20160342877 | Mullen et al. | Nov 2016 | A1 |
| 20160342878 | Mullen et al. | Nov 2016 | A1 |
| 20160342879 | Mullen et al. | Nov 2016 | A1 |
| 20160342880 | Mullen et al. | Nov 2016 | A1 |
| 20170286817 | Mullen et al. | Oct 2017 | A1 |
| 20170300796 | Mullen et al. | Oct 2017 | A1 |
| 20180053079 | Cloutier et al. | Feb 2018 | A1 |
| 20180060881 | Mullen et al. | Mar 2018 | A1 |
| 20190042903 | Cloutier et al. | Feb 2019 | A1 |
| 20190065928 | Mullen et al. | Feb 2019 | A1 |
| 20190197387 | Mullen et al. | Jun 2019 | A1 |
| 20190340484 | Mullen et al. | Nov 2019 | A1 |
| 20200082383 | Mullen et al. | Mar 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 10 2008 060513 | Jun 2010 | DE |
| 05210770 | Aug 1993 | JP |
| WO9852735 | Nov 1998 | WO |
| WO0247019 | Jun 2002 | WO |
| WO04012352 | Feb 2004 | WO |
| WO06066322 | Jun 2006 | WO |
| WO06080929 | Aug 2006 | WO |
| WO06105092 | Oct 2006 | WO |
| WO06116772 | Nov 2006 | WO |
| WO08064403 | Jun 2008 | WO |
| WO06078910 | Sep 2009 | WO |
| Entry |
|---|
| U.S. Appl. No. 60/594,300, Poidomani et al. |
| U.S. Appl. No. 60/675,388, Poidomani et al. |
| The Bank Credit Card Business. Second Edition, American Bankers Association, Washington, D.C., 1996. |
| A Day in the Life of a Flux Reversal. http://www.phrack/org/issues.html?issue=37&id=6#article. As viewed on Apr. 12, 2010. |
| Dynamic Virtual Credit Card Numbers. http://homes.cerias.purdue.edu/˜jtli/paper/fc07.pdf. As viewed on Apr. 12, 2010. |
| English translation of JP 05210770 A. |
| USPTO, International Search Report, dated Oct. 16, 2012. |
| EPO, Partial Supplementary Search Report, App No. 12783038.8, dated Nov. 19, 2014. |
| EPO Search Report App No. 12783038.8, dated Mar. 17, 2015. |
| Number | Date | Country | |
|---|---|---|---|
| 20120290449 A1 | Nov 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61484547 | May 2011 | US | |
| 61484588 | May 2011 | US | |
| 61484566 | May 2011 | US | |
| 61484576 | May 2011 | US |
