US20120290472A1 - Systems and devices for mobile payment acceptance - Google Patents

Systems and devices for mobile payment acceptance Download PDF

Info

Publication number
US20120290472A1
US20120290472A1 US13/468,462 US201213468462A US2012290472A1 US 20120290472 A1 US20120290472 A1 US 20120290472A1 US 201213468462 A US201213468462 A US 201213468462A US 2012290472 A1 US2012290472 A1 US 2012290472A1
Authority
US
United States
Prior art keywords
mobile device
example
payment
card
user
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
US13/468,462
Inventor
Jeffrey D. Mullen
Christopher J. Rigatti
Michael T. Wallace
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Dynamics Inc
Original Assignee
Dynamics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US201161484576P priority Critical
Priority to US201161484588P priority
Priority to US201161484547P priority
Priority to US201161484566P priority
Application filed by Dynamics Inc filed Critical Dynamics Inc
Priority to US13/468,462 priority patent/US20120290472A1/en
Assigned to DYNAMICS INC. reassignment DYNAMICS INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: WALLACE, MICHAEL T.
Assigned to DYNAMICS INC. reassignment DYNAMICS INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MULLEN, JEFFREY D., RIGATTI, CHRISTOPHER J.
Publication of US20120290472A1 publication Critical patent/US20120290472A1/en
Application status is Pending legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/22Payment schemes or models
    • G06Q20/223Payment schemes or models based on the use of peer-to-peer networks
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices using wireless devices
    • G06Q20/322Aspects of commerce using mobile devices [M-devices]
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices using wireless devices
    • G06Q20/327Short range or proximity payments by means of M-devices
    • G06Q20/3278RFID or NFC payments by means of M-devices
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices
    • G06Q20/34Payment architectures, schemes or protocols characterised by the use of specific devices using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/352Contactless payments by cards
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/385Use of an alias or a single-use code
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes

Abstract

A mobile device may provide payment acceptance for purchases, payments and/or money transfers by accepting payment information from a powered, or a non-powered, card using a contactless communication channel formed between the card and the mobile device. The payment information may be communicated by the mobile device to network entities that may be used to settle such purchase, payment and/or money transfer transactions. The mobile device may, for example, accept more than one payment account to split a purchase among several payment accounts. A user of a mobile device may, for example, store payment information within the mobile device for future purchases. A user of a mobile device may, for example, request checkout options using the mobile device, such as customizing receipt delivery, annotating receipts with comments and categorizing purchases for customized accounting reports.

Description

    CROSS-REFERENCE TO RELATED APPLICATION
  • 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 (Attorney Docket No. D/063 PROV), 61/484,566, titled “SYSTEMS AND METHODS FOR A MOBILE ELECTRONIC WALLET,” filed May 10, 2011 (Attorney Docket No. D/064 PROV), 61/484,576, titled “SYSTEMS AND METHODS FOR MOBILE AUTHORIZATIONS,” filed May 10, 2011 (Attorney Docket No. D/065 PROV), and 61/484,588, titled “SYSTEMS AND METHODS FOR CONTACTLESS COMMUNICATION MECHANISMS FOR CARDS AND MOBILE DEVICES,” filed May 10, 2011 (Attorney Docket No. D/066 PROV) all of which are hereby incorporated by reference herein in their entirety.
  • BACKGROUND OF THE INVENTION
  • This invention relates to mobile devices and related systems.
  • SUMMARY OF THE INVENTION
  • A mobile device is provided that may be used as a point-of-sale terminal. A contactless communication channel may, for example, be formed between the mobile device and a payment card to communicate payment information from the payment card to the mobile device. The mobile device may, for example, use the communicated payment information to complete a purchase transaction that may be initiated by the mobile device. Accordingly, for example, no payment information need reside on the mobile terminal to complete a payment transaction. Instead, an application may be remotely activated, or a user of a mobile device may activate an application on the mobile device, that allows the mobile device to accept payment information directly from a payment card before and/or during a payment transaction.
  • A mobile device may, for example, provide a browsing activity where goods and/or services may be located for purchase on a website (e.g., an Amazon or eBay website). An application may, for example, be executed on a mobile device that may communicate with a checkout application running on a website. Payment information may be exchanged directly from a user's payment card to the checkout application using the user's mobile device. In so doing, for example, a mobile device may be used as a contactless payment acceptance terminal.
  • A user may be provided an option of storing payment information associated with a payment card within a memory of the mobile device. Accordingly, for example, a mobile device may store payment information associated with one or more payment accounts. In so doing, for example, a mobile device may store multiple payment accounts that may be recalled from a memory of the mobile device at the user's request 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. For example, a card having RFID capability may communicate with an RFID device of a mobile device when the card comes within a distance (e.g., up to 2 inches) of the mobile device. Accordingly, for example, a card type (e.g., a powered card or a non-powered card) may be identified by the mobile device.
  • A non-powered card may, for example, communicate one, two, and/or three tracks of magnetic stripe data to a mobile device via a contactless interface of the mobile device. Accordingly, a processor of a mobile device may identify an account type (e.g., credit or debit) that may be associated with the non-powered 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 (e.g., information within discretionary data fields) to a contactless interface of a mobile device. In so doing, for example, the additional information may be analyzed 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 information (e.g., discretionary data) received from the powered card.
  • A mobile device may 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 and payment information is communicated to the mobile device by the payment card. Once entered, a mobile device may, for example, access a server associated with the payment card's issuing entity to validate the PIN. Alternately, for example, a processor of a mobile device may compare the PIN entry against local memory contents of the mobile device to validate the entered PIN.
  • As per another example, a mobile device may validate a payment card by requiring that the physical payment card be present during a payment transaction. Accordingly, for example, a mobile device may require that a physical payment card be tapped against the mobile device so that a contactless communication channel may be formed between the payment card and the mobile device to verify the identity of the payment card. Accordingly, for example, identifying information communicated by the payment card to the mobile device may be compared against information previously stored within a memory of the mobile device that may be associated with the payment card.
  • One or more payment cards may, for example, be presented to a mobile device to complete a purchase transaction. Accordingly, for example, split-payment options may be offered by a mobile device. In so doing, for example, a first payment card may be tapped against a mobile device and accepted by the mobile device as a first form of partial payment, a second payment card may be tapped against a mobile device and accepted by the mobile device as a second form of partial payment, and so on. A mobile device may, for example, allow a user to select an amount for each partial payment and may settle each partial payment amount with each respective issuer of each payment card presented for partial payment.
  • A mobile device may provide checkout options to a user. For example, a mobile device may allow a user to associate purchase categories (e.g., groceries, auto repair, or entertainment) to purchases transacted by the mobile device so that the user may prepare a more detailed accounting of his or her expenditures. As per another example, a rewards card may be tapped against a mobile device so that rewards card information may be credited with purchases transacted by the mobile device.
  • A mobile device may provide receipt delivery options to a user. For example, a mobile device may allow a user to select one of many receipt delivery options (e.g., text messaging, email or autonomous delivery to accounting software executed by a processor of the mobile device). Other receipt options may be provided by a mobile device in a graphical format (e.g., a barcode) so that proof-of-purchase may be verified by a reader (e.g., a barcode reader).
  • Money transfers may, for example, be transacted by a mobile device. One or more payment accounts (e.g., a car account or a utility account) may be selected by a user of a mobile device to receive a payment transacted by the mobile device. Payment information may be recalled from memory and/or entered by a user of the mobile device and then communicated to network entities by the mobile device to complete payment transactions.
  • Person to person transfers may, for example, be transacted by a mobile device. A user of a mobile device may, for example, tap a payment card against the mobile device to communicate source account information to the mobile device where funds are to be withdrawn. A person receiving a transfer of funds may, for example, tap his or her payment card against a device (e.g., a mobile device) to communicate target account information where funds are to be deposited. A mobile device may, for example, gather source and target account information and communicate such information to network entities to complete the funds transfer transaction.
  • A mobile device may, for example, provide a scanning capability (e.g., via a camera) to scan images (e.g., barcodes) that may be analyzed by a processor of the mobile device. Accordingly, for example, a mobile device may be used to scan product information from a product tag (e.g., a barcode) to select an item for purchase. As items are selected for purchase, scanned information is processed and displayed by the mobile device to produce a summary of items that may be selected for purchase. The mobile device may, for example, collect payment information from a payment card via a contactless communication channel and then use the payment information to complete a purchase transaction for the items scanned by the mobile device.
  • A mobile device may access electronic billing information via one or more communication capabilities of the mobile device. A merchant (e.g., a restaurant) may provide access to an electronic tab generated by the merchant (e.g., a bill generated by a restaurant for a dinner for two). Items billed by the merchant may be accessed by a user of a mobile device and displayed by the mobile device to produce a summary of items billed. The mobile device may, for example, collect payment information from a payment card via a contactless communication channel and then use the payment information to complete a purchase transaction for the billed items.
  • 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 point-of-sale terminal. Accordingly, for example, a mobile device may accept payment information from any payment card, communicate such payment information via a 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 user 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.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • 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:
  • FIG. 1 is an illustration of a mobile devices constructed in accordance with the principles of the present invention;
  • FIG. 2 is an illustration of a network topology constructed in accordance with the principles of the present invention;
  • FIG. 3 is an illustration of a mobile payment system constructed in accordance with the principles of the present invention;
  • FIG. 4 is an illustration of a display screen constructed in accordance with the principles of the present invention;
  • FIG. 5 is an illustration of a display screen constructed in accordance with the principles of the present invention;
  • FIG. 6 is an illustration of a display screen constructed in accordance with the principles of the present invention;
  • FIG. 7 is an illustration of a display screen constructed in accordance with the principles of the present invention;
  • FIG. 8 is an illustration of a display screen constructed in accordance with the principles of the present invention;
  • FIG. 9 is an illustration of a display screen constructed in accordance with the principles of the present invention;
  • FIG. 10 is an illustration of a display screen constructed in accordance with the principles of the present invention;
  • FIG. 11 is an illustration of a display screen constructed in accordance with the principles of the present invention;
  • FIG. 12 is an illustration of a display screen constructed in accordance with the principles of the present invention;
  • FIG. 13 is an illustration of a display screen constructed in accordance with the principles of the present invention;
  • FIG. 14 is an illustration of a display screen constructed in accordance with the principles of the present invention;
  • FIG. 15 is an illustration of a display screen constructed in accordance with the principles of the present invention;
  • FIG. 16 is an illustration of a display screen constructed in accordance with the principles of the present invention;
  • FIG. 17 is an illustration of a display screen constructed in accordance with the principles of the present invention;
  • FIG. 18 is an illustration of a display screen constructed in accordance with the principles of the present invention;
  • FIG. 19 is an illustration of a display screen constructed in accordance with the principles of the present invention;
  • FIG. 20 is an illustration of a display screen constructed in accordance with the principles of the present invention;
  • FIG. 21 is an illustration of a display screen constructed in accordance with the principles of the present invention;
  • FIG. 22 is an illustration of a mobile funds transfer system constructed in accordance with the principles of the present invention;
  • FIG. 23 is an illustration of a mobile payment system constructed in accordance with the principles of the present invention;
  • FIG. 24 is an illustration of a mobile payment system constructed in accordance with the principles of the present invention;
  • FIG. 25 is an illustration of a mobile payment system constructed in accordance with the principles of the present invention; and
  • FIG. 26 is a flow chart of processes constructed in accordance with the principles of the present invention.
  • DETAILED DESCRIPTION OF THE INVENTION
  • FIG. 1 shows mobile device 100. Mobile device 100 may be any mobile device, such as a mobile telephonic device (e.g., cell phone), a PDA, an electronic tablet, an MP3 player, or a locating device (e.g., a GPS device). Accordingly, mobile device 100 may be operated in a mobile environment while a user of mobile device 100 goes about his or her daily activities (e.g., driving, shopping, walking, dining, and exercising). In addition, for example, mobile device 100 may perform multiple functions simultaneously (e.g., a person may carry on a conversation while at the same time browsing and purchasing products on the Internet).
  • 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 payment 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.
  • FIG. 1 shows architecture 150. User interface 152 may, for example, be included within architecture 150 to allow user interaction with architecture 150. For example, a dedicated key pad or keyboard may be included within user interface 152 to allow alphanumeric data entry into architecture 150.
  • 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 in accordance with a character position identified 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, 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 FIG. 1) to establish a communications channel with an associated cellular station. In so doing, for example, a mobile device (e.g., mobile device 100 of FIG. 1) may exchange information (e.g., voice, text, data, or multimedia) with one or more terrestrial networks (e.g., the internet or a payment network) via an associated cellular station. As per another example, transceiver 156 may exchange information with one or more other mobile devices via one or more associated cellular stations.
  • 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 FIG. 1) may directly connect to a wired and/or a wireless network via any one or more wireless standards (e.g., Bluetooth or Wi-Fi) to exchange information with other devices that may be connected to the wired and/or wireless network. In so doing, for example, a wired and/or wireless network may be accessed by a mobile device without first accessing a mobile network via a cellular station of a mobile network.
  • 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) 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 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 FIG. 1). Persons skilled in the art will appreciate that executable application code may be communicated to architecture 150 via any one or more interfaces of architecture 150 (e.g., user interface 152, display 154, transceiver 156, and/or contactless communication device 162).
  • Application data (e.g., 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 FIG. 1). Once recalled, processor 158 may communicate the payment card data via transceiver 156 and/or contactless communication device 162 to complete a financial transaction.
  • FIG. 2 shows network topology 200 that may include, for example, mobile device 202 (e.g., a mobile telephonic device, a PDA, an electronic tablet, a laptop, a GPS unit, or an MP3 player). Mobile device 202 may, for example, include a contactless interface that may initiate, sustain, and/or terminate communication channel 226 between contactless device 204 and mobile device 202. Contactless device 204 and mobile device 202 may communicate via channel 226 using any number of contactless mediums, which may include for example, visible, audible, capacitive, electromagnetic, magnetic, and/or RF mediums.
  • Mobile device 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 device 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 device 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 device 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 device 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.
  • Contactless device 204 may, for example, be a powered card or a non-powered card (e.g., a powered payment card or a non-powered payment card). Accordingly, for example, payment information (e.g., a payment account number and a card expiration date) may be communicated from contactless device 204 to mobile device 202 in support of a financial transaction being conducted by mobile device 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 device 202 via an access point (e.g., wireless access point 208 or cellular network access infrastructure 206). Mobile device 202 may, for example, complete a purchase transaction by first obtaining required payment information from contactless device 204 and then 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 device 202 for authorization of a purchase. Once authorized, payment transaction information may be recorded onto a receipt that may be delivered to mobile device 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).
  • A payment receipt may, for example, be provided to mobile device 202 as a proof-of-purchase object (e.g., a barcode) that may be provided to a display of mobile device 202 and read by other computing equipment (e.g., a barcode scanner) for proof-of-purchase confirmation.
  • A mobile device (e.g., mobile device 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 device 224 may communicate payment information to merchant terminal 218 to complete a financial transaction. In so doing, for example, mobile device 224 may first receive payment information via contactless communication channel 230 from contactless device 222 (e.g., a non-powered card), temporarily store the received payment information within a memory of mobile device 224, and forward the payment information onto merchant terminal 218 to complete a financial transaction. As per another example, mobile device 224 may provide previously stored financial information associated with one or more payment cards (e.g., one or more non-powered payment cards). Accordingly, for example, payment information may be recalled from a memory of mobile device 224 and communicated to merchant terminal 218 via contactless communication channel 228 to complete a financial transaction using merchant terminal 218.
  • FIG. 3 shows system 300, which may include mobile device 302 and payment card 304. Mobile device 302 may, for example, be a laptop computer, a PDA, a mobile telephonic device (e.g., a smartphone), an MP3 player, a GPS, or any other mobile device. Display 308 may be a touch-sensitive display (e.g., sensitive to a change in capacitance). Payment card 304 may, for example, be a powered payment card or a non-powered payment card.
  • Mobile device 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 device 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 device 302 to establish a proximity relationship that forms a communication channel between payment card 304 and mobile device 302. As per another example, payment card 304 may be brought within a proximity distance (e.g., up to two inches) of mobile device 302 to establish a contactless communication channel between mobile device 302 and payment card 304.
  • A processor of mobile device 302 may, for example, execute application code that may generate a graphical user interface (GUI) onto display 308 of mobile device 302. Message 306 of a GUI may invite a user of mobile device 302 to begin a mobile payment by tapping a payment card against display 308. As per another example, by tapping payment card 304 against mobile device 302, mobile device 302 may autonomously determine that a mobile payment is desired and then generate a mobile payment GUI onto display 302.
  • Mobile device 302 may, for example, autonomously determine a type of card that may be tapped against it. For example, a processor of mobile device 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 device 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 device 302. In so doing, for example, a contactless communication channel may be established where data is transferred from payment card 304 to mobile device 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 device 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 device 302 and light pulses may generate a data stream from mobile device 302 to payment card 304.
  • FIG. 4 shows GUI 400, that may be generated by a processor of a mobile device and provided onto a display of the mobile device. GUI 400 may, for example, generate results of a card detection operation that may be performed by a processor of a mobile device. For example, card information may be exchanged between a card and a mobile device via a contactless communication channel that may identify a type of card that is being presented to the mobile device. Any type of card may be detected by a processor of a mobile device, such as for example, an airline card, a travel card, a bank card, a healthcare card, an identification card, and a loyalty rewards card. A card number communicated to a mobile device may, for example, be indicative of a card type (e.g., bank card 404) that is presented to a mobile device. Accordingly, for example, a processor of a mobile device may identify a card type presented to the mobile device by analyzing a card number received from the card and may indicate the identified card type via GUI 400 (e.g., the identified card type may be generated onto GUI 400 having a different graphical presentation than the other card types listed).
  • A GUI may, for example, provide navigation aids. A GUI may, for example, provide navigation aids that may be touch sensitive. For example, GUI 400 may include navigation aids 406 and 408 to enable a user to revert to a previous GUI or advance to a subsequent GUI. Accordingly, for example, a user may touch an area on a display of a mobile device that displays a navigation aid to activate the touched navigation aid. In so doing, for example, a user may touch navigation aid 406 to revert to the previous GUI or a user may touch navigation aid 408 to advance to the next GUI.
  • FIG. 5 shows GUI 500, that may be generated by a processor of a mobile device and provided onto a display of the mobile device. GUI 500 may, for example, generate results of a payment card detection operation that may be performed by a processor of a mobile device. A non-powered payment card may, for example, communicate a single payment card number that may be associated with a number of payment options (e.g., debit, credit, or points). Accordingly, for example, GUI 500 may be generated to allow a user an opportunity to select which payment option (e.g., credit option 502) from a number of payment options is to be used to settle a payment transaction. Once identified, a payment option selection (e.g., credit option 502) may be communicated by a mobile device to an issuer of the payment card to settle the transaction using the selected payment option.
  • As per another example, a powered payment card may include a user interface to allow a user to select from a number of payment options. A button on a powered payment card may, for example, be associated with one payment method (e.g., pay with credit) and another button may, for example, be associated with another payment method (e.g., pay with points). Data associated with the selected payment method may be communicated from a powered payment card to a mobile device. Accordingly, for example, a processor of a mobile device may detect the payment method communicated by a powered payment card (e.g., as communicated within a discretionary data field) and may autonomously generate a graphical representation of the payment method selected (e.g., GUI 500 may autonomously generate a graphical representation that credit method 502 was selected).
  • FIG. 6 shows GUI 600 that may be generated by a processor of a mobile device and provided onto a display of the mobile device. GUI 600 may, for example, include a bank card validation screen as may be generated by a processor of a mobile device. A mobile device may, for example, challenge a user of the mobile device to enter a PIN that may be associated with a payment card (e.g., VISA credit 602) that was previously presented to the mobile device for payment. GUI 600 may, for example, generate virtual pin pad 606 that may include touch-sensitive buttons having alphanumeric indicia associated with each button. A user may touch one or more buttons of pin pad 606 that may correspond to respective characters of a PIN and an indication of the user's selection may appear within area 604. Characters displayed within area 604 may, for example, be hidden for security purposes.
  • Activation of virtual button 608 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 payment. 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 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 606 to enter the one or more characters of a PIN.
  • FIG. 7 shows GUI 700 that may be generated by a processor of a mobile device and provided onto a display of the mobile device. GUI 700 may, for example, include a bank card validation screen as may be generated by a processor of a mobile device. A mobile device may, for example, challenge a user of the mobile device to enter a security code that may be associated with a payment card (e.g., VISA credit 702) that was previously presented to the mobile device for payment. Such a security code (e.g., a CVV code) may, for example, be printed on the back of the payment card.
  • GUI 700 may, for example, generate virtual pin pad 706 that may include touch-sensitive buttons having alphanumeric indicia associated with each button. A user may touch one or more buttons of pin pad 706 that may correspond to respective characters of a security code and an indication of the user's selection may appear within area 704. Characters displayed within area 704 may, for example, be hidden for security purposes.
  • Activation of virtual button 708 may, for example, cause a processor of a mobile device to compare a security code entered by a user of the mobile device to a security code that may be associated with the payment card presented to the mobile device for payment. The security code 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 security code entered. Alternately, for example, the mobile device may communicate the security code to the issuing bank for a remote validation of the security code 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 706 to enter the one or more characters of a security code.
  • FIG. 8 shows GUI 800 that may be generated by a processor of a mobile device and provided onto a display of the mobile device. GUI 800 may, for example, include a bank card validation screen as may be generated by a processor of a mobile device. A mobile device may, for example, maintain memory of one or more payment cards previously presented to the mobile device for payment. A mobile device may, for example, allow a user to store payment information within the mobile device that may be associated with a payment card to be used at some point in the future.
  • Accordingly, for example, a user may recall payment information previously stored in memory of a mobile device in order to complete a purchase transaction using the mobile device. In order to validate that a user of a mobile device is actually the owner of payment information recalled from memory of the mobile device, GUI 800 may challenge the user to present the physical payment card whose associated payment information was recalled from memory. In so doing, for example, GUI 800 may prevent a fraudulent user of a mobile device from authorizing a purchase using payment information stored in memory of the mobile device that is not owned by the fraudulent user.
  • A user may, for example, be required to present a physical payment card to GUI 800 by placing (or tapping) the physical payment card within a proximity of a display of a mobile device that is generating GUI 800. In so doing, for example, a contactless communication channel (e.g., an RFID communication channel) may be established between the physical payment card and the mobile device, such that payment information may be communicated from the physical payment card to the mobile device. Upon verification that the communicated payment information matches payment information stored in memory of the mobile device, the payment information may be validated and authorized to be communicated from the mobile device to a network entity (e.g., a payment server or the issuer of the payment card) for settlement of the purchase transaction.
  • FIG. 9 shows GUI 900 that may be generated by a processor of a mobile device and provided onto a display of the mobile device. GUI 900 may, for example, include validation area 902 as generated by a processor of a mobile device. Validation area 902 may, for example, include one or more data exchange areas (e.g., data exchange areas 904 and 906). Icon 904 may, for example, be generated by GUI 900 within an area of a display of a mobile device that may be sensitive to touch (e.g., an area that may be sensitive to a capacitance change). Area 906 may, for example, be generated by GUI 900 within an area of a display of a mobile device that may generate pulses of light.
  • A powered payment card may be validated for use by a mobile device through an exchange data with the powered payment card via data exchange areas 904 and 906. For example, a powered payment card may be pressed against validation area 902 so that a touch simulation device of the powered payment card aligns with data exchange area 904 and a light sensing device 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 validation information so that payment card information stored within the mobile device may be validated for use.
  • A mobile device may, for example, include a motion capture device (e.g., a camera) and a powered payment card may, for example, include a light source (e.g., an LED). Accordingly, for example, information (e.g., validation information) may be exchanged between a mobile device and a powered payment card such that information communicated by the powered payment card may be communicated as a series of light pulses while the camera of the mobile device captures the series of light pulses. A processor of the mobile device may construe the series of light pulses as information that may be used, for example, as validation information.
  • FIG. 10 shows GUI 1000 that may be generated by a processor of a mobile device and provided onto a display of the mobile device. GUI 1000 may be generated, for example, after payment card information has been communicated by either of a non-powered payment card or a powered payment card to a mobile device. A user of a mobile device may, for example, elect whether to store such payment card information within a memory location of the mobile device. If a user chooses not to store payment information received from a payment card (e.g., as elected by selection of radio button 1004), a mobile device may delete all payment information previously received from a payment card after the payment information is used to complete a purchase transaction. Accordingly, a user wishing to use the same payment card to complete a payment transaction in the future is required to present the payment card to the mobile device so that the payment card may communicate payment card information to the mobile device in order to complete the payment transaction. If a user chooses to store payment information received from a payment card (e.g., as elected by selection of radio button 1002), a mobile device may store a portion of, or all, payment information previously received from a payment card in accordance with a user's preference.
  • FIG. 11 shows GUI 1100 that may be generated by a processor of a mobile device and provided onto a display of the mobile device. GUI 1100 may, for example, offer storage options to a user of a mobile device that has elected to store a portion of, or all, payment card information previously communicated to the mobile device by a non-powered card or a powered card. A data storage option may, for example, be selected by a user of a mobile device (e.g., by touching a portion of text box 1102) that stores only a portion (e.g., an expiration date and payment card account number) of the payment card information into a memory of the mobile device. Accordingly, for example, a payment card may communicate one, two, and/or three tracks of magnetic stripe data to a mobile device, but the only payment information stored within a memory of the mobile device upon selection of text box 1102 is the expiration date and the payment card account number. All remaining information that may have been communicated by the payment card to the mobile device may be deleted by the mobile device.
  • Selection of text box 1104 may, for example, cause all payment information communicated by a payment card to a mobile device to be stored within a memory of the mobile device. Accordingly, for example, a mobile device may use a portion or all of the payment information stored within its memory to complete a purchase transaction. However, payment card validation information (e.g., a PIN or security code) may still be required to be entered by a user of the mobile device before the mobile device may complete a purchase transaction with the stored payment information.
  • Selection of box 1106 may, for example, cause all payment information communicated by a payment card to a mobile device to be stored within a memory of the mobile device. All validation information (e.g., a PIN or security code) that may be entered by a user of the mobile device to validate payment information received from a payment card may also be stored within a memory of the mobile device. Accordingly, for example, a mobile device may use a portion or all of the payment information, including validation information, stored within its memory to complete a purchase transaction.
  • Selection of box 1108 may, for example, cause all payment information, including discretionary data fields, communicated by a payment card to a mobile device to be stored within a memory of the mobile device. A powered payment card may, for example, allow a user of the powered payment card to select one or more options that may be associated with the powered payment card. A powered payment card may, for example, communicate indicia associated with the one or more selected options within discretionary data fields of magnetic stripe data that may be communicated to a mobile device.
  • For example, a user of a powered payment card may elect to pay for a purchase using rewards points by pressing a button on the powered payment card that is associated with a rewards points payment option. Accordingly, for example, a powered payment card may insert a rewards points payment code within a discretionary data field of a first, a second and/or a third track of magnetic stripe data and may communicate all track data, including the discretionary data field, to a mobile device. In so doing, for example, a processor of a mobile device may detect such a payment code within a discretionary data field and may store payment information within a memory of the mobile device that is indicative of the rewards points payment code contained within the discretionary data field.
  • FIG. 12 shows GUI 1200 that may be generated by a processor of a mobile device and provided onto a display of the mobile device. GUI 1200 may, for example, offer a split-payment option to a user of a mobile device, such that the user may elect to split payment for a selected purchase between two or more payment accounts. The mobile device may, for example, communicate payment information for each of the selected split-payment accounts to respective network entities (e.g., issuer and payment servers) of the selected split-payment accounts in order to settle the amounts owing on each of the selected split-payment accounts.
  • A user may, for example, select option 1202 (e.g., by tapping a payment card against a display of a mobile device or by presenting a payment card within proximity to the mobile device). In so doing, for example, a contactless communication channel (e.g., an RFID communication channel) may be established between the payment card and the mobile device so that payment information associated with the payment card may be communicated by the payment card to the mobile device and used as a split-payment account for a selected purchase.
  • An alternate contactless communication channel may be established, for example, by pressing a payment card against portion 1208. Accordingly, for example, a payment card may communicate payment information associated with the payment card to a processor of a mobile device by simulating a series of touches at a location within portion 1208 (e.g., at icon 1210) and the processor of the mobile device may communicate information to the payment card by generating a series of light pulses at a location within portion 1208 (e.g., at location 1212). In so doing, for example, payment information associated with the payment card may be received by a processor of a mobile device and used as a split-payment account to partially cover the purchase price of a selected purchase.
  • Other contactless communication channels may be established. For example, a processor of a payment card may communicate payment information to a mobile device by generating a series of light pulses (e.g., via an LED of the payment card), which may be captured by a camera of the mobile device and construed by a processor of the mobile device as payment information. As per another example, a payment card may communicate payment information using audible sounds that may be received by a microphone of a mobile device and construed by a processor of the mobile device as payment information.
  • A payment account may, for example, be selected from a memory of the mobile device (e.g., by selecting radio button 1204). Associated payment information may, for example, be selectively retrieved from a memory of the mobile device and used by the mobile device as a split-payment account in partial payment for a selected purchase. Alternately, for example, a split-payment option may be declined by a user of a mobile device (e.g., by selecting radio button 1206).
  • FIG. 13 shows GUI 1300 that may be generated by a processor of a mobile device and provided onto a display of the mobile device. GUI 1300 may, for example, provide a summary of split-payment methods that may have been selected by a user of a mobile device. Portion 1302, for example, may display an amount owing for a particular selected purchase. Portions 1304-1308 may, for example, include an alphanumeric entry box to allow a user of a mobile device to input payment amounts (e.g., currency or points) that he or she wishes to apply towards a total amount owing as may be displayed in portion 1302. Portions 1304-1308 may, for example, include those payment accounts that a user of a mobile device previously selected as split-payment accounts.
  • Accordingly, for example, a user may elect to charge $10 against a VISA credit account, $35 against a M/C debit account, and 500 rewards points earned by the VISA credit account towards full payment of a $50 amount owing for a particular selected purchase. In so doing, for example, a mobile device may communicate with selected network entities (e.g., issuer and payment servers) to provide transaction information associated with each split-payment account selected, so that each amount owing may be settled.
  • Portions 1310-1314 may, for example, include alphanumeric entry boxes to allow a user of a mobile device to make comments on each account selected as a split-payment account. Accordingly, for example, a mobile device may communicate notes that may be entered by a user within portions 1310-1314 to, for example, a payment server. In so doing, for example, receipts and/or account statements that may be generated by a network entity (e.g., an issuer or a payment server) may include such notes so that a user of a mobile device, upon receipt of such receipts and/or account statements, may be reminded of his or her thought process when such a split-payment was transacted.
  • FIG. 14 shows GUI 1400 that may be generated by a processor of a mobile device and provided onto a display of the mobile device. GUI 1400 may, for example, offer checkout options to a user of a mobile device to allow a level of integration between the user and one or more issuers of associated payment accounts used by the mobile device in settlement of a selected purchase.
  • For example, a user may utilize billing tag list 1402 to categorize a selected purchase into one of many purchase categories. A user's physical presence may, for example, be at a fast-food establishment where the user may select a food purchase from the fast-food establishment's website using a browser of the user's mobile device. Payment information used to settle a transaction associated with the selected food purchase may be collected and/or generated by the mobile device and forwarded onto a payment server and/or an associated issuer for settlement. In addition, the mobile device may forward a billing tag selected from billing tag list 1402 to the associated issuer, so that the associated issuer may label the selected transaction on a billing statement using the selected billing tag. In so doing, for example, a user may customize an accounting of the issuer's billing statement by using a mobile device to communicate payment information and billing tags associated with selected purchases to track expenditures within the various purchase categories of billing tag list 1402.
  • A user of a mobile device may select receipt delivery options for each purchase that may be transacted using a mobile device. For example, a receipt delivery list may be generated by a processor of a mobile device so that a user of the mobile device may select a receipt delivery option. Accordingly, for example, the selected receipt delivery option along with payment information may be communicated by a mobile device to a payment server and the payment server (or other entity) may direct a delivery of the receipt based upon the receipt delivery option received.
  • A user may, for example, request delivery of a purchase receipt via text messaging (e.g., by selecting receipt delivery option 1406). In so doing, for example, a mobile device may complete a purchase transaction with an entity of a payment network (e.g., a payment server) and may further request that the payment server deliver a receipt to the mobile device in a text message format. Accordingly, for example, in addition to providing payment information to the payment server, a mobile device may also provide a text message address (e.g., an SMS text message address) to the payment server. In so doing, for example, the mobile device may receive a receipt of the completed purchase transaction from the payment server via a text message at the text message address provided by the mobile device.
  • As per another example, a multimedia message (e.g., an MMS message containing rich content) may be received by a mobile device from a payment server in the form of, for example, a graphical image (e.g., barcode), such that the barcode may be used as a proof-of-purchase (e.g., proof-of-purchase of an airline ticket and an associated barcode that gains access by the user of the mobile device to a particular seating assignment on the airplane.)
  • A receipt (e.g., a receipt received via multimedia messaging) may, for example, provide rewards to a user of the mobile device for completing payment transactions via a mobile device. For example, a mobile device may communicate indicia to a payment server that identifies a payment transaction as a mobile payment transaction. The communicated mobile payment indicia may, for example, trigger a payment server to not only provide a receipt for the purchase transaction to the mobile device, but also to provide a multimedia game that may be executed by the mobile device. As per an example, an animated trivia question may be communicated to a mobile device via an MMS message upon completion of a mobile payment transaction. Upon successfully answering the animated trivia question, a user of the mobile device may receive another MMS message that contains a coupon for free merchandise from the merchant whose goods were just purchased. As per another example, a receipt received from a payment server may itself contain coupons for discounted or free merchandise without requiring that a user of the mobile device perform any further actions beyond completing a mobile payment purchase with a mobile device.
  • A user may, for example, request delivery of a purchase receipt via email (e.g., by selecting receipt delivery option 1408). In so doing, for example, an email address associated with the user may be provided by the mobile device to a payment server in addition to any required payment information that may be required to complete a purchase transaction. Accordingly, for example, a payment server may address a receipt to an email address received from a mobile device during a mobile payment transaction.
  • A user may, for example, request delivery of a purchase receipt (e.g., by selecting receipt delivery option 1410) via a format that may be compatible with an accounting software package (e.g., QuickBooks). For example, a mobile device may allow a user to categorize a particular purchase within a particular expense account (e.g., an office supply expense account) during a purchase transaction. Once the purchase transaction is completed, an electronic receipt may be communicated to the mobile device that may be tagged with the categorized expense account (e.g., the accounting software package may have its own address that receipts may be delivered to). In so doing, for example, an accounting software package that may be executing on the mobile device may autonomously access the electronic receipt from its own address and may autonomously enter the expense in the correct category so that all purchases made by the mobile device may be correctly accounted for within the accounting software package.
  • A user may, for example, request delivery of a purchase receipt (e.g., by selecting receipt delivery option 1412) via a format that may be compatible with the bank that issued the selected payment account. Accordingly, for example, a payment server may forward a receipt of the purchase transaction to the issuing bank and the issuing bank may format the receipt for delivery with the user's month-end account statement.
  • A user may, for example, enter comments about a purchase transaction that may be included within a receipt. For example, a user may enter comments 1404 that may remind the user to include the receipt within his or her tax records because the purchase may be deemed as tax deductible. Accordingly, for example, comments 1404 may accompany payment information communicated by a mobile device to a payment server. In so doing, for example, a payment server may add comments 1404 to a receipt generated by the payment server and may forward the receipt with the added comments to the user of the mobile device as dictated by the receipt delivery options requested by the user of the mobile device.
  • FIG. 15 shows GUI 1500 that may be generated by a processor of a mobile device and provided onto a display of the mobile device. GUI 1500 may, for example, offer a check-out option to a user of a mobile device, such that the user may elect to apply a rewards card to a selected purchase in order for the rewards card to accrue points for the purchase. The mobile device may, for example, submit rewards card information and transaction information to respective issuers of the rewards account so that the respective issuers may credit the rewards account accordingly.
  • A user may, for example, select option 1502 (e.g., by tapping a rewards card against a display of a mobile device or by presenting a rewards card within proximity to the mobile device). In so doing, for example, a contactless communication channel (e.g., an RFID communication channel) may be established between the rewards card and the mobile device so that information associated with the rewards card may be communicated by the rewards card to the mobile device.
  • An alternate contactless communication channel may be established, for example, by pressing a rewards card against portion 1508. Accordingly, for example, a rewards card may communicate information associated with the rewards card to a processor of a mobile device by simulating a series of touches within portion 1508 (e.g., at icon 1510) and the processor of the mobile device may communicate information to the rewards card by generating a series of light pulses within portion 1508 (e.g., at location 1512). In so doing, for example, rewards information associated with the rewards card may be received by a mobile device and communicated to an issuer of the rewards card so that the rewards account may be updated with the purchase transaction information.
  • Other contactless communication channels may be established. For example, a processor of a rewards card may communicate rewards information to a mobile device by generating a series of light pulses (e.g., via an LED of the rewards card), which may be captured by a camera of the mobile device and construed by a processor of the mobile device as rewards information. As per another example, a payment card may communicate payment information using audible sounds that may be received by a microphone of a mobile device and construed by a processor of the mobile device as payment information.
  • A rewards account may, for example, be selected from a memory of the mobile device (e.g., by selecting radio button 1504). Associated rewards information may, for example, be selectively retrieved from a memory of the mobile device and communicated by the mobile device to an issuer of the rewards account so that the rewards account may be credited with the selected purchase.
  • A user of a mobile device may, for example, place an order for a rewards card by selecting radio button 1506. Accordingly, for example, a mobile device may communicate payment information to a payment server to complete a purchase transaction and may also communicate a request that a rewards account be created. A payment server may, for example, forward the rewards account creation request to an issuer of a rewards account along with details of the purchase transaction, so that the issuer may first create the rewards account and may then credit the account according to the purchase transaction. Accordingly, for example, an electronic version of a newly created rewards card (e.g., a graphical representation of a newly created rewards card) may, for example, be communicated to a mobile device which may, for example, include a barcode representation of the rewards account information. In addition, rewards card information may, for example, be added to a memory of a mobile device for future access.
  • FIG. 16 shows GUI 1600 that may be generated by a processor of a mobile device and provided onto a display of the mobile device. GUI 1600 may, for example, challenge a user of a mobile device to enter an access code that may be required to authenticate a purchase transaction. GUI 1600 may, for example, include virtual keyboard 1604 to allow a user of a mobile device to enter such an access code. Alternately, for example, a manual input interface of a mobile device (e.g., a keyboard or a keypad) may be used to enter such an access code.
  • As a user of a mobile device enters each character of an access code, portion 1602 may reflect such entry. Such entries may, for example, be reflected within portion 1602 as protected characters (e.g., the actual value of each character may be blocked out) to protect the security and safety of the entered access code. Once an entered access code is verified and authenticated by a mobile device, the mobile device may complete the requested purchase transaction.
  • FIG. 17 shows GUI 1700 that may be generated by a processor of a mobile device and provided onto a display of the mobile device. GUI 1700 may, for example, include portion 1702 that may display a graphical representation of a proof-of-purchase (e.g., a barcode). Such a proof-of-purchase may be communicated to a mobile device via a network entity (e.g., a payment server) upon completion of a purchase transaction by the mobile device.
  • Accordingly, for example, portion 1702 may graphically display a proof-of-purchase that may be recognized by a reader (e.g., a barcode reader). In so doing, for example, a system that may include a barcode reader may verify the validity of a proof-of-purchase barcode, which may then allow a user of a mobile device displaying such a barcode to enjoy the goods and/or services purchased by the user via the mobile device as acknowledged by the verified barcode. As per one example, such a verified barcode may allow entry onto an airplane having a seat assignment that is encoded within the barcode. As per another example, a user may have made an on-line purchase of an appliance using his or her mobile device and may have requested pick-up of the purchased appliance at an appliance inventory warehouse. Upon arrival at the appliance inventory warehouse, a user may retrieve an electronic proof-of-purchase (e.g., a barcode) from a memory of the mobile device that was received by the user's mobile device upon completion of the appliance purchase transaction. A reader (e.g., a barcode reader) at the appliance inventory warehouse may read the user's barcode directly from a display of the user's mobile device, verify that a purchase was completed by the user's mobile device, and may authorize the appliance for pickup by the user.
  • FIG. 18 shows GUI 1800 that may be generated by a processor of a mobile device and provided onto a display of the mobile device. GUI 1800 may, for example, enable a funds transfer to one or more financial accounts. GUI 1800 may, for example, enable a transfer of funds (e.g., by selecting radio button 1802) directly from one or more financial accounts into one or more financial accounts. GUI 1800 may, for example, generate a communication channel with a recipient of a funds transfer (e.g., by selecting radio button 1804) and may allow the recipient to interactively determine the financial account that is to receive the transferred funds.
  • FIG. 19 shows GUI 1900 that may be generated by a processor of a mobile device and provided onto a display of the mobile device. GUI 1900 may, for example, enable a funds transfer to one or more accounts. GUI 1900 may, for example, allow a user of a mobile device to select an object (e.g., by selecting an entry within menu list 1902) that may be associated with the funds transfer. GUI 1900 may, for example, allow a user to select an account (e.g., by selecting an entry within menu list 1904) that may be associated with the object selected within menu list 1902.
  • Accordingly, for example, a mobile device may include a memory within which a user may enter one or more potential recipients of a funds transfer. A processor of a mobile device may, for example, list each potential recipient of a funds transfer within menu list 1902. A user of a mobile device may, for example, select a recipient of a funds transfer by activating (e.g., touching) an entry within menu list 1902 that corresponds to the selected recipient. As per an example, a user's funds transfer recipient list, as may be reflected by menu list 1902, may include persons, financial accounts, inanimate objects, or any other type of object.
  • Once a selected funds transfer recipient is selected within menu list 1902, menu list 1904 may be populated. Accordingly, for example, a mobile device may include a memory within which a user may enter one or more accounts that may be associated with one or more potential recipients of a funds transfer. A processor of a mobile device may, for example, list each account in menu list 1904 that may be associated with the selected recipient of menu list 1902. A user of a mobile device may, for example, select an account for a funds transfer by activating (e.g., touching) an entry within menu list 1904 that corresponds to the selected account. As per an example, a user's funds transfer account list, as may be reflected by menu list 1904, may include any account that may be associated with the selected recipient of menu list 1902.
  • FIG. 20 shows GUI 2000 that may be generated by a processor of a mobile device and provided onto a display of the mobile device. GUI 2000 may, for example, enable a funds transfer from a source account (e.g., an account associated with a payment card that is tapped against a display of a mobile device) to a target account (e.g., a car loan account). Portion 2002 may, for example, list account details that may be associated with a target account (e.g., an account number associated with a car loan, the payoff amount, and the amount due). Portion 2002 may, for example, include details that may be associated with a target account that a mobile device has collected from a network entity (e.g., a bank) via a network connection between the mobile device and the network entity.
  • Portion 2004 (e.g., an alphanumeric entry box) may, for example, allow a user of a mobile device to enter an amount to be transferred (e.g., an amount that is equal to the minimum amount due on an installment payment agreement). GUI 2000 may, for example, request an identification of a source account from which the amount will be transferred. As per an example, a user of a mobile device may tap a payment card against a display of the mobile device to establish a contactless communication channel between the payment card and the mobile device within which payment information may be communicated from the payment card to the mobile device. As per another example, a payment card may communicate payment information to a mobile device via a series of touch simulations (e.g., changes in capacitance generated by a payment card that may be detected by a touch-sensitive display of a mobile device). A series of light pulses, or audible information, for example, may be communicated by the payment card to the mobile device in order to communicate payment information.
  • GUI 2000 may, for example, display a summary of payment information that may have been received by a mobile device from a payment card via a contactless communication channel. For example, portion 2006 may be displayed by GUI 2000 to allow a user of a mobile device to confirm the identity of a payment account from which an amount of money will be transferred. Once confirmed, the mobile device may communicate with network entities (e.g., an issuer of the source account and a bank associated with the target account) to complete the money transfer.
  • FIG. 21 shows GUI 2100 that may be generated by a processor of a mobile device and provided onto a display of the mobile device. GUI 2100 may, for example, enable a funds transfer to an account associated with a person. A recipient may, for example, interactively select an account into which the funds will be transferred. Accordingly, for example, contact list 2102 may be displayed by GUI 2100 as a list of potential recipients of a money transfer. Contact method list 2104 may, for example, by displayed by GUI 2100 as a list of methods that may be used to contact the recipient as selected within contact list 2102. In so doing, for example, a person within contact list 2102 (e.g., Trace) may be selected by a user of a mobile device to be the recipient of a funds transfer and the recipient may be contacted, for example, in accordance with a method selected in contact method list 2104 (e.g., transfer alert).
  • FIG. 22 shows system 2200, which may include mobile device 2202, receiving device 2204, and network 2210. Mobile device 2202 may be a device used to coordinate a money transfer and receiving device 2204 may be a device used to coordinate receipt of a money transfer. Receiving device may, for example, be a mobile device. Receiving device, for example, may not be a mobile device (e.g., a desktop computer). Devices 2202-2204 may communicate via network 2210, which may include any combination of cellular network resources, wireless network resources, and/or wired network resources.
  • Mobile device 2202 may, for example, include a processor that may render money transfer GUI 2206 onto a display of mobile device 2202. GUI 2206 may, for example, pause while a user of mobile device 2202 selects a payment account from which a money transfer may be withdrawn. Accordingly, for example, mobile device 2202 may wait until a payment card is brought within a proximity to, or a touch relationship with, mobile device 2202 (e.g., a payment card may be tapped onto a display of mobile device 2202). Alternately, for example, a payment card may communicate with mobile device 2202 using any number of contactless methods (e.g., using light, sound, capacitive, magnetic or electromagnetic communication). In so doing, for example, mobile device 2202 may establish a contactless communication channel with a payment card in which payment information is communicated from the payment card to mobile device 2202 and is summarized onto GUI 2206 for review by a user of mobile device 2202. A user of mobile device 2202 may enter an amount of money for transfer, may verify a money amount for transfer, and may enter a message to be communicated to receiving device 2204.
  • Mobile device 2202 may communicate payment information received from a payment card along with information received from a user of mobile device 2202 to a network entity (e.g., an issuer) where, for example, authorization of the transfer amount from the account selected is performed. Once authorized, mobile device 2202 may communicate a transfer alert along with a transfer alert message to receiving device 2204. Receiving device 2204 may, for example, present a transfer alert along with the associated transfer alert message onto GUI 2208. A user of receiving device 2204 may respond to the transfer alert message received from mobile device 2202 by sending an acknowledgment message to mobile device 2202 via network 2210.
  • A user of receiving device 2204 may, for example, be asked to enter account information that is to be used as the receiving account for the money transfer. Accordingly, for example, a user of receiving device 2204 may provide such account information any number of ways. For example, a payment card associated with a receiving account may be brought within a proximity, or a touching, relationship to receiving device 2204. In so doing, for example, a contactless communication channel (e.g., an RFID channel) may be formed to communicate such information. Alternately, a payment card may communicate with receiving device 2204 using any number of contactless methods (e.g., using light, sound, capacitive, magnetic or electromagnetic communication). A user of receiving device 2204 may verify the receive account information as it may be displayed onto GUI 2208.
  • Receiving device 2204 may, for example, communicate information associated with a receiving account to mobile device 2202 via network 2210. Accordingly, for example, mobile device 2202 may coordinate the money transfer via network 2210 with network entities (e.g., an issuer of the account used to provide money to transfer and an issuer of the account used to receive money for transfer). Once the money transfer is completed, an acknowledgment message may be displayed onto GUI 2206 by a processor of mobile device 2202 and an acknowledgment message may be communicated by mobile device 2202 to receiving device 2204 and then displayed onto GUI 2208 by a processor of receiving device 2204.
  • FIG. 23 shows system 2300, which may include a mobile device 2302, a powered or non-powered payment card 2304, a remote application 2308 and network 2306. Mobile device 2302 may, for example, access remote application 2308 via network 2306 in order to complete a purchase transaction. Accordingly, for example, payment card 2304 may communicate payment information to mobile device 2302 via contactless communication channel 2312 and mobile device 2302 may communicate the payment information to remote application 2308 via communication channel 2310 to complete the purchase transaction.
  • Contactless communication channel 2312 may be any type of contactless communication channel, such as for example, an RF, capacitive, audible, visible, electromagnetic, or magnetic communication channel. Contactless communication channel 2312 may be a two-way communication channel, where mobile device 2302 may communicate with payment card 2304 in order to, for example, enhance data communication between mobile device 2302 and payment card 2304.
  • As per one example, payment card 2304 may communicate payment information (e.g., one, two, and/or three tracks of magnetic stripe data) to mobile device 2302 after payment card 2304 is tapped against mobile device 2302. Remote application 2308 may, for example, be an on-line payment application that does not require a fully populated magnetic stripe message to complete a purchase transaction, but may only require a subset of a fully populated magnetic stripe message (e.g., account number and expiration date). Accordingly, for example, mobile device 2302 may filter payment information received from payment card 2304 to only include the subset of information that may be required by remote application 2308 and may communicate only the filtered payment information to remote application 2308 to complete the purchase transaction.
  • In general, for example, mobile device 2302 may filter payment information received from payment card 2304 into a filtered subset of payment data that may be required by remote application 2308 to complete a purchase transaction. In so doing, for example, mobile device 2302 may customize a payment message to remote application 2308 that includes only the filtered subset of data that is needed by remote application 2308 to complete the purchase transaction.
  • As per another example, mobile device 2302 may query payment card 2304 via contactless communication channel 2312 for only a subset of payment information that may be required by remote application 2308 to complete a purchase transaction. Accordingly, for example, a processor of payment card 2304 may receive the request and may only supply the requested payment information via contactless communication channel 2312 instead of communicating a complete magnetic stripe message.
  • FIG. 24 shows system 2400, which may include a mobile device 2402, a payment card 2404, a rewards card 2416, and items to be purchased 2410-2414. Mobile device 2402 may, for example, include a scanning device (e.g., a camera) that may be used to capture images (e.g., barcode images). Accordingly, for example, a user of mobile device 2402 may activate an application within mobile device 2402 that generates GUI 2408 and that activates a camera to capture barcode images. A processor of mobile device 2402 may, for example, analyze captured barcode images to extract information from the barcode images and construe the extracted information as data input. Accordingly, for example, a camera of mobile device 2402 may be used to scan barcodes of items that the user wishes to purchase and a processor of mobile device 2402 may analyze the scanned information to keep a running total of items selected for purchase. In so doing, for example, a user of mobile device 2402 may wander through a shopping market while scanning barcode labels of items for purchase (e.g., items 2410-2414).
  • Mobile device 2402 may access a network (e.g., a local Wi-Fi hotspot) within a shopping market to determine those items that may be offered at a discount to rewards members of the shopping market. Accordingly, for example, a user may scan barcode image 2418 of rewards card 2416 to obtain an instant credit for discounted items for purchase. As per another example, rewards card 2416 may establish a contactless communication channel with mobile device 2402 so that rewards card 2416 may communicate rewards account information to mobile device 2402 via any one of a number of contactless communication mediums (e.g., RF, capacitive, audible, visible, electromagnetic, or magnetic communication mediums).
  • Once a user of mobile device 2402 finishes shopping, the user may present payment card 2404 to mobile device 2402 for payment. Accordingly, for example, contactless communication channel 2406 (e.g., an RF, capacitive, audible, visible, electromagnetic, or magnetic communication channel) may be created and payment information may be communicated from payment card 2404 to mobile device 2402 so that mobile device 2402 may complete the purchase transaction with a network entity (e.g., an issuer of payment card 2404).
  • FIG. 25 shows system 2500, which may include mobile device 2502 and payment card 2504. Mobile device 2502 may interact with a merchant establishment (e.g., a restaurant) to gain entry into a user's tab at the merchant's establishment (e.g., a food and alcohol bill generated by the restaurant). Accordingly, for example, a user may monitor each item on the bill, enter an additional amount into the bill (e.g., a tip), and then pay the bill all from the convenience of the user's mobile device 2502.
  • Interaction with a merchant establishment may be accomplished any number of ways. For example, mobile device 2502 may access a local Wi-Fi hotspot and may communicate information (e.g., an email address or text messaging address) to the merchant that identifies a user of mobile device 2502. Accordingly, for example, a merchant may send a message (e.g., an email or text message) to the user-supplied address that may contain a link to the user's bill. A user may, for example, click on the link, enter a pass code to gain entry to the user's bill, and then monitor the bill being generated onto a display of mobile device 2502 via GUI 2508.
  • As per another example, mobile device 2502 may place a phone call to a merchant's phone number to establish a communication channel (e.g., a data call) between the merchant server and mobile device 2502. The merchant server may, for example, render GUI 2508 onto a display of mobile device 2502 so that a user of mobile device 2502 may directly interact with the merchant server.
  • GUI 2508 may be rendered onto a display of mobile device 2502 to allow a user to remotely interact with his or her bill. For example, a user's meal tab at a restaurant may be itemized by GUI 2508 and an alphanumeric entry box (e.g., box 2510) may allow the user to enter additional data (e.g., add a tip to the bill). A user may, for example, review a total to be charged, verify such a total, and then present payment card 2504 to mobile device 2502 to settle the total amount. In so doing, for example, contactless communication channel 2506 may receive payment information from payment card 2504 via any number of contactless communication mediums (e.g., RF, capacitive, audible, visible, electromagnetic, or magnetic communication mediums) and may communicate such payment information to a network entity (e.g., an issuer of payment card 2504) to complete a purchase transaction for the total amount of the user's bill.
  • FIG. 26 shows flow charts for process sequences 2610-2650. Process sequence 2610 may, for example, execute a payment application on a mobile device (e.g., as in step 2611) to request a user of the mobile device to present a payment card to the mobile device. In step 2612, a user may present a payment card (e.g., tap a payment card onto a display of a mobile device) to begin a payment transaction. In step 2613, a contactless communication channel (e.g., an RF, capacitive, audible, visible, electromagnetic, or magnetic communication channel) may be generated between a payment card and a mobile device to communicate payment information from the payment card to the mobile device. In step 2614, a purchase may be completed by a mobile device by communicating received payment information to network entities to settle a payment transaction.
  • Process sequence 2620 may, for example, autonomously detect that a payment card is in a touching or a proximity relationship to a mobile device (e.g., as in step 2621). In step 2622, a contactless communication channel (e.g., an RF, capacitive, audible, visible, electromagnetic, or magnetic communication channel) may be generated between a payment card and a mobile device to communicate payment information from the payment card to the mobile device. In step 2623, a purchase may be completed by a mobile device by communicating received payment information to network entities to settle a payment transaction.
  • Step 2631 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 2632 and 2633, 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 2641 of sequence 2640 may include selecting items for purchase using a mobile device. A mobile device may, for example, include a scanning device (e.g., a camera) that may be used by a mobile device to capture images of barcodes that may be associated with items for purchase (e.g., grocery items in a grocery store). Accordingly, for example, a mobile device may collect images of barcodes and a processor of the mobile device may analyze the images to retrieve information (e.g., item description and cost) of each item scanned. Each item's description, cost and other information may, for example, be displayed on a GUI that may be generated by a processor and presented to a display of the mobile device as in step 2642. A payment card may, for example, be presented to the mobile device (e.g., as in step 2643) and payment information may be exchanged between the payment card and the mobile device (e.g., as in step 2644) via a contactless communication channel (e.g., an RF, capacitive, audible, visible, electromagnetic, or magnetic communication channel). In step 2645, a mobile device may communicate received payment information to network entities (e.g., a payment server and/or an issuer) to complete the transaction.
  • In step 2651 of sequence 2650, for example, a mobile device may remotely access an electronic bill. For example, a merchant (e.g., a restaurant) may provide access to a bill (e.g., a restaurant tab for food and beverages) to a patron of the merchant via that patron's mobile device. As per one example, a merchant may provide a link to a bill via a message (e.g., an email message or a text message) that may be sent by the merchant to the patron's mobile device or that may be sent by the patron's mobile device to the merchant. The patron may click on the link and may be taken to a website that may provide access to the patron's tab via a browser that may be executing on the patron's mobile device. As per another example, a data call between a patron's mobile device and a merchant may execute an application (e.g., locally on the patron's mobile device and/or remotely on a merchant's server) to allow a patron to review his or her bill.
  • Each item on the patron's bill may, for example, include a description, cost and other information and may be displayed on a GUI that may be generated by a processor and presented to a display of the mobile device as in step 2652. A payment card may, for example, be presented to the mobile device (e.g., as in step 2653) and payment information may be exchanged between the payment card and the mobile device (e.g., as in step 2654) via a contactless communication channel (e.g., an RF, capacitive, audible, visible, electromagnetic, or magnetic communication channel). In step 2655, a mobile device may communicate received payment information to network entities (e.g., a payment server and/or an issuer) to complete the transaction.
  • 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 mobile 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.

Claims (21)

1. A method, comprising:
accessing a network using a mobile device;
selecting an object for purchase from said network using said mobile device;
communicating payment information from a payment card to said mobile device using a contactless communication channel; and
communicating said payment information from said mobile device to said network to complete a purchase transaction for said object.
2. A method, comprising:
communicating source account information to a first mobile device using a first contactless communication channel;
communicating target account information to a second mobile device using a second contactless communication channel;
communicating said target account information from said second mobile device to said first mobile device; and
coordinating a money transfer from said source account into said target account using said first mobile device.
3. The method of claim 1, wherein said mobile device is a laptop computer.
4. The method of claim 1, wherein said mobile device is a PDA.
5. The method of claim 1, wherein said mobile device is a phone.
6. The method of claim 1, wherein said contactless communication channel is an RFID communication channel.
7. The method of claim 1, wherein said mobile device and said payment card are brought within a proximity distance of up to two inches to establish said contactless communication channel.
8. The method of claim 1, wherein said payment card is a powered card.
9. The method of claim 1, wherein said payment card is a non-powered card.
10. The method of claim 1, wherein said payment card simulates a series of touches to a display of said mobile device to establish at least a portion of said contactless communication channel.
11. The method of claim 1, wherein said mobile device communicates an optical data stream to said payment card to establish at least a portion of said contactless communication channel.
12. The method of claim 2, wherein a powered card communicates said target account information.
13. The method of claim 2, wherein a non-powered card communicates said target account information.
14. The method of claim 2, wherein a powered card communicates said source account information.
15. The method of claim 2, wherein a non-powered card communicates said source account information.
16. The method of claim 2, wherein said first mobile device is a laptop computer.
17. The method of claim 2, wherein said first mobile device is a PDA.
18. The method of claim 2, wherein said first mobile device is a phone.
19. The method of claim 2, wherein said second mobile device is a laptop computer.
20. The method of claim 2, wherein said second mobile device is a PDA.
21. The method of claim 2, wherein said second mobile device is a phone.
US13/468,462 2011-05-10 2012-05-10 Systems and devices for mobile payment acceptance Pending US20120290472A1 (en)

Priority Applications (5)

Application Number Priority Date Filing Date Title
US201161484576P true 2011-05-10 2011-05-10
US201161484588P true 2011-05-10 2011-05-10
US201161484547P true 2011-05-10 2011-05-10
US201161484566P true 2011-05-10 2011-05-10
US13/468,462 US20120290472A1 (en) 2011-05-10 2012-05-10 Systems and devices for mobile payment acceptance

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US13/468,462 US20120290472A1 (en) 2011-05-10 2012-05-10 Systems and devices for mobile payment acceptance

Publications (1)

Publication Number Publication Date
US20120290472A1 true US20120290472A1 (en) 2012-11-15

Family

ID=47139649

Family Applications (4)

Application Number Title Priority Date Filing Date
US13/468,462 Pending US20120290472A1 (en) 2011-05-10 2012-05-10 Systems and devices for mobile payment acceptance
US13/468,625 Pending US20120286936A1 (en) 2011-05-10 2012-05-10 Systems and methods for contactless communication mechanisms for cards and mobile devices
US13/468,571 Pending US20120286928A1 (en) 2011-05-10 2012-05-10 Systems and methods for mobile authorizations
US13/468,518 Pending US20120290449A1 (en) 2011-05-10 2012-05-10 Systems and methods for a mobile electronic wallet

Family Applications After (3)

Application Number Title Priority Date Filing Date
US13/468,625 Pending US20120286936A1 (en) 2011-05-10 2012-05-10 Systems and methods for contactless communication mechanisms for cards and mobile devices
US13/468,571 Pending US20120286928A1 (en) 2011-05-10 2012-05-10 Systems and methods for mobile authorizations
US13/468,518 Pending US20120290449A1 (en) 2011-05-10 2012-05-10 Systems and methods for a mobile electronic wallet

Country Status (4)

Country Link
US (4) US20120290472A1 (en)
EP (1) EP2707847A4 (en)
CA (1) CA2835508A1 (en)
WO (1) WO2012154915A1 (en)

Cited By (68)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140025457A1 (en) * 2012-07-17 2014-01-23 Mastercard International Incorporated Method and system for deal redemption by electronic wallet
US20140108235A1 (en) * 2012-10-16 2014-04-17 American Express Travel Related Services Company, Inc. Systems and Methods for Payment Settlement
US20140156517A1 (en) * 2012-11-30 2014-06-05 Wal-Mart Stores, Inc. Splitting a purchase among multiple parties using an electronic receipt after the transaction
US20140222597A1 (en) * 2013-02-04 2014-08-07 Mastercard International Incorporated Intelligent mobile payment system and method
US20140330727A1 (en) * 2011-10-12 2014-11-06 Technology Business Management Limited ID Authentication
US20150154581A1 (en) * 2009-10-13 2015-06-04 Square, Inc. Systems and methods for dynamic receipt generation with environmental information
US20150170132A1 (en) * 2013-12-18 2015-06-18 PayRange Inc. Method and System for Presenting Representations of Payment Accepting Unit Events
US20150206122A1 (en) * 2013-09-26 2015-07-23 Seth Daniel Elliott Point of sale normalization and extension services for invoice management
US9134994B2 (en) 2013-12-18 2015-09-15 PayRange Inc. Method and system for updating firmware using a mobile device as a communications bridge
US20150278800A1 (en) * 2006-09-24 2015-10-01 Rfcyber Corporation Method and apparatus for mobile payments
WO2015154552A1 (en) * 2014-04-10 2015-10-15 福建联迪商用设备有限公司 Sound-wave payment method and system
US9256873B2 (en) 2013-12-18 2016-02-09 PayRange Inc. Method and device for retrofitting an offline-payment operated machine to accept electronic payments
US9262771B1 (en) 2015-01-30 2016-02-16 PayRange Inc. Method and system for providing offers for automated retail machines via mobile devices
US20160062608A1 (en) * 2011-01-10 2016-03-03 Apple Inc. Button functionality
US9317846B2 (en) * 2011-12-01 2016-04-19 At&T Intellectual Property I, L.P. Point of sale for mobile transactions
USD755183S1 (en) 2013-12-18 2016-05-03 Payrange, Inc. In-line dongle
US9349089B1 (en) 2011-05-23 2016-05-24 Dynamics Inc. Systems and methods for sensor mechanisms for magnetic cards and devices
USD763905S1 (en) 2015-01-30 2016-08-16 PayRange Inc. Display screen or portion thereof with animated graphical user interface
USD763888S1 (en) 2015-01-30 2016-08-16 PayRange Inc. Display screen or portion thereof with graphical user interface
USD764532S1 (en) 2015-01-30 2016-08-23 PayRange Inc. Display screen or portion thereof with animated graphical user interface
USD773508S1 (en) 2015-01-30 2016-12-06 PayRange Inc. Display screen or portion thereof with a graphical user interface
US9619741B1 (en) 2011-11-21 2017-04-11 Dynamics Inc. Systems and methods for synchronization mechanisms for magnetic cards and devices
US9646750B1 (en) 2012-11-30 2017-05-09 Dynamics Inc. Dynamic magnetic stripe communications device with stepped magnetic material for magnetic cards and devices
US9659246B1 (en) 2012-11-05 2017-05-23 Dynamics Inc. Dynamic magnetic stripe communications device with beveled magnetic material for magnetic cards and devices
US9710745B1 (en) 2012-02-09 2017-07-18 Dynamics Inc. Systems and methods for automated assembly of dynamic magnetic stripe communications devices
US9842330B1 (en) 2016-09-06 2017-12-12 Apple Inc. User interfaces for stored-value accounts
WO2017213785A1 (en) * 2016-06-11 2017-12-14 Apple Inc. User interface for transaction
US9847999B2 (en) 2016-05-19 2017-12-19 Apple Inc. User interface for a device requesting remote authorization
US9852368B1 (en) 2009-08-17 2017-12-26 Dynamics Inc. Advanced loyalty applications for powered cards and devices
US9875473B2 (en) 2013-12-18 2018-01-23 PayRange Inc. Method and system for retrofitting an offline-payment operated machine to accept electronic payments
US9911123B2 (en) 2014-05-29 2018-03-06 Apple Inc. User interface for payments
US9940637B2 (en) 2015-06-05 2018-04-10 Apple Inc. User interface for loyalty accounts and private label accounts
US9965911B2 (en) 2015-12-07 2018-05-08 Capital One Services, Llc Electronic access control system
US10024682B2 (en) 2015-02-13 2018-07-17 Apple Inc. Navigation user interface
US10066959B2 (en) 2014-09-02 2018-09-04 Apple Inc. User interactions for a mapping application
US10108951B2 (en) 2012-11-30 2018-10-23 Walmart Apollo, Llc Splitting a purchase among multiple parties using an electronic receipt after the transaction
WO2018200121A1 (en) * 2017-04-24 2018-11-01 Mastercard International Incorporated A digital wallet payment system and process
US10142835B2 (en) 2011-09-29 2018-11-27 Apple Inc. Authentication with secondary approver
USD836118S1 (en) 2015-01-30 2018-12-18 Payrange, Inc. Display screen or portion thereof with an animated graphical user interface
US10255595B2 (en) 2015-02-01 2019-04-09 Apple Inc. User interface for payments
US10281999B2 (en) 2014-09-02 2019-05-07 Apple Inc. Button functionality
US10296889B2 (en) 2008-09-30 2019-05-21 Apple Inc. Group peer-to-peer financial transactions
US10332079B2 (en) 2015-06-05 2019-06-25 Apple Inc. User interface for loyalty accounts and private label accounts for a wearable device
US10339530B1 (en) 2019-02-21 2019-07-02 Capital One Services, Llc Touch authentication of multiple users or operating modes for a transaction card
US10380573B2 (en) 2008-09-30 2019-08-13 Apple Inc. Peer-to-peer financial transaction devices and methods
US10395156B1 (en) 2012-05-15 2019-08-27 Dynamics Inc. Cards, devices, systems, methods and dynamic security codes
US10395128B2 (en) 2017-09-09 2019-08-27 Apple Inc. Implementation of biometric authentication
US10410200B2 (en) 2016-03-15 2019-09-10 Square, Inc. Cloud-based generation of receipts using transaction information
US10424007B2 (en) 2015-12-07 2019-09-24 Mastercard International Incorporated Systems and methods for utilizing vehicle connectivity in association with payment transactions
US10425129B1 (en) 2019-02-27 2019-09-24 Capital One Services, Llc Techniques to reduce power consumption in near field communication systems
USD862501S1 (en) 2015-01-30 2019-10-08 PayRange Inc. Display screen or portion thereof with a graphical user interface
US10438437B1 (en) 2019-03-20 2019-10-08 Capital One Services, Llc Tap to copy data to clipboard via NFC
US10467445B1 (en) 2019-03-28 2019-11-05 Capital One Services, Llc Devices and methods for contactless card alignment with a foldable mobile device
US10467622B1 (en) 2019-02-01 2019-11-05 Capital One Services, Llc Using on-demand applications to generate virtual numbers for a contactless card to securely autofill forms
US10482363B1 (en) 2010-03-02 2019-11-19 Dynamics Inc. Systems and methods for detection mechanisms for magnetic cards and devices
US10484384B2 (en) 2011-09-29 2019-11-19 Apple Inc. Indirect authentication
US10489781B1 (en) 2018-10-02 2019-11-26 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10498401B1 (en) 2019-07-15 2019-12-03 Capital One Services, Llc System and method for guiding card positioning using phone sensors
US10496808B2 (en) 2016-10-25 2019-12-03 Apple Inc. User interface for managing access to credentials for use in an operation
US10505738B1 (en) 2018-10-02 2019-12-10 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10506426B1 (en) 2019-07-19 2019-12-10 Capital One Services, Llc Techniques for call authentication
US10510074B1 (en) 2019-02-01 2019-12-17 Capital One Services, Llc One-tap payment using a contactless card
US10511443B1 (en) 2018-10-02 2019-12-17 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10516447B1 (en) 2019-06-17 2019-12-24 Capital One Services, Llc Dynamic power levels in NFC card communications
US10521180B1 (en) 2011-01-04 2019-12-31 AQ Corporation NFC-enabled apparatus and method of operation thereof
US10523708B1 (en) 2019-03-18 2019-12-31 Capital One Services, Llc System and method for second factor authentication of customer support calls
US10521579B2 (en) 2017-09-09 2019-12-31 Apple Inc. Implementation of biometric authentication
US10535062B1 (en) 2019-03-20 2020-01-14 Capital One Services, Llc Using a contactless card to securely share personal data stored in a blockchain

Families Citing this family (118)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10169692B2 (en) * 2007-12-24 2019-01-01 Dynamics Inc. Credit, security, debit cards and the like with buttons
US9318108B2 (en) 2010-01-18 2016-04-19 Apple Inc. Intelligent automated assistant
US10147077B2 (en) * 2010-09-21 2018-12-04 Mastercard International Incorporated Financial transaction method and system having an update mechanism
US9547861B2 (en) * 2011-05-11 2017-01-17 Mark Itwaru System and method for wireless communication with an IC chip for submission of pin data
KR101829254B1 (en) * 2011-05-23 2018-02-19 삼성전자 주식회사 Operating Method For Personnel Social Information And System supporting the same
US8538845B2 (en) 2011-06-03 2013-09-17 Mozido, Llc Monetary transaction system
JP2013020609A (en) * 2011-06-13 2013-01-31 Kazunori Fujisawa Authentication system
US20130181054A1 (en) * 2011-07-06 2013-07-18 Chris Juarez Durham System and method for processing bar-code enabled cards
CN102346861A (en) * 2011-09-16 2012-02-08 中兴通讯股份有限公司 Method and terminal for managing RFID (Radio Frequency Identification Device) card
US10360557B2 (en) 2015-04-14 2019-07-23 Capital One Services, Llc Dynamic transaction card protected by dropped card detection
US10482453B2 (en) 2015-04-14 2019-11-19 Capital One Services, Llc Dynamic transaction card protected by gesture and voice recognition
US10332102B2 (en) * 2011-10-17 2019-06-25 Capital One Services, Llc System, method, and apparatus for a dynamic transaction card
US10474941B2 (en) 2015-04-14 2019-11-12 Capital One Services, Llc Dynamic transaction card antenna mounting
US9208488B2 (en) 2011-11-21 2015-12-08 Mozido, Inc. Using a mobile wallet infrastructure to support multiple mobile wallet providers
US10438196B2 (en) 2011-11-21 2019-10-08 Mozido, Inc. Using a mobile wallet infrastructure to support multiple mobile wallet providers
US8880027B1 (en) * 2011-12-29 2014-11-04 Emc Corporation Authenticating to a computing device with a near-field communications card
WO2013116726A1 (en) * 2012-02-03 2013-08-08 Ebay Inc. Adding card to mobile wallet using nfc
US8763896B2 (en) * 2012-02-23 2014-07-01 XRomb Inc. System and method of loading a transaction card and processing repayment on a mobile device
US10097496B2 (en) 2012-05-09 2018-10-09 Apple Inc. Electronic mail user interface
US10235014B2 (en) 2012-05-09 2019-03-19 Apple Inc. Music user interface
US20140052524A1 (en) * 2012-06-06 2014-02-20 Robert Andersen Systems and Methods for Providing Transaction Rewards
CN102737308B (en) * 2012-06-08 2015-08-12 中兴通讯股份有限公司 The method and system of a kind of mobile terminal and inquiry smart card information thereof
US20140074655A1 (en) * 2012-09-07 2014-03-13 David Lim System, apparatus and methods for online one-tap account addition and checkout
US20140074704A1 (en) * 2012-09-11 2014-03-13 Cashstar, Inc. Systems, methods and devices for conducting transactions with electronic passbooks
US20140089154A1 (en) * 2012-09-21 2014-03-27 Egan Schulz Colored card scroller
US10235692B2 (en) 2012-10-17 2019-03-19 Groupon, Inc. Consumer presence based deal offers
US20140108247A1 (en) 2012-10-17 2014-04-17 Groupon, Inc. Peer-To-Peer Payment Processing
US9325807B1 (en) * 2012-11-01 2016-04-26 Government Employees Insurance Company (GEICO) Methods and systems for providing digital identification cards for mobile applications
US9092712B2 (en) * 2012-11-02 2015-07-28 Flextronics Ap, Llc Embedded high frequency RFID
US9959007B2 (en) * 2012-12-05 2018-05-01 Facebook, Inc. Card-stack interface
US9344404B2 (en) 2013-01-31 2016-05-17 Dell Products L.P. System and method for synchronizing connection credentials
FI20135155A (en) * 2013-02-21 2014-08-22 Op Palvelut Oy Communication between merchant and customer
US9965756B2 (en) * 2013-02-26 2018-05-08 Digimarc Corporation Methods and arrangements for smartphone payments
US20140258110A1 (en) * 2013-03-11 2014-09-11 Digimarc Corporation Methods and arrangements for smartphone payments and transactions
US9830588B2 (en) * 2013-02-26 2017-11-28 Digimarc Corporation Methods and arrangements for smartphone payments
CN105190659A (en) * 2013-02-26 2015-12-23 数字标记公司 Methods and arrangements for smartphone payments and transactions
US9934523B1 (en) 2013-03-05 2018-04-03 Square, Inc. On-device directory search
US9576286B1 (en) * 2013-03-11 2017-02-21 Groupon, Inc. Consumer device based point-of-sale
US9852409B2 (en) 2013-03-11 2017-12-26 Groupon, Inc. Consumer device based point-of-sale
US10482511B1 (en) * 2013-03-12 2019-11-19 Groupon, Inc. Employee profile for customer assignment, analytics and payments
US9361613B2 (en) * 2014-02-17 2016-06-07 Samsung Pay, Inc. System and method for a baseband nearfield magnetic stripe data transmitter
US9776071B2 (en) 2013-05-09 2017-10-03 Mattel, Inc. Resonant coils for use with games and toys
US20140358794A1 (en) * 2013-06-04 2014-12-04 Ncr Corporation Techniques for credit card processing
CA2914673A1 (en) * 2013-06-04 2014-12-11 Ims Solutions Inc. Remote control and payment transactioning system using natural language, vehicle information, and spatio-temporal cues
WO2014197336A1 (en) 2013-06-07 2014-12-11 Apple Inc. System and method for detecting errors in interactions with a voice-based digital assistant
US20150006376A1 (en) * 2013-06-27 2015-01-01 Ebay Inc. Conductive payment device
US9053405B1 (en) 2013-08-27 2015-06-09 Flextronics Ap, Llc Printed RFID circuit
US10001817B2 (en) 2013-09-03 2018-06-19 Apple Inc. User interface for manipulating user interface objects with magnetic properties
US9898642B2 (en) 2013-09-09 2018-02-20 Apple Inc. Device, method, and graphical user interface for manipulating user interfaces based on fingerprint sensor inputs
US9928493B2 (en) 2013-09-27 2018-03-27 Groupon, Inc. Systems and methods for providing consumer facing point-of-sale interfaces
ES2532653B1 (en) 2013-09-30 2016-01-05 Intelligent Data, S.L. Electronic payment device
JP6393325B2 (en) 2013-10-30 2018-09-19 アップル インコーポレイテッドApple Inc. Display related user interface objects
US20150134518A1 (en) * 2013-11-14 2015-05-14 Google Inc. Pre-authorized online checkout
US20150149291A1 (en) * 2013-11-26 2015-05-28 Najla Ferraz Abdala Magnetic card transaction system based in cloud computing and simulated magnetic cards
US10311425B2 (en) * 2014-01-14 2019-06-04 International Business Machines Corporation Integrating mobile payment application with other mobile applications while preventing security exposures
WO2015107346A1 (en) * 2014-01-15 2015-07-23 Iaxept Limited Authentication method and system
US9560746B1 (en) 2014-01-24 2017-01-31 Multek Technologies, Ltd. Stress relief for rigid components on flexible circuits
US9311639B2 (en) * 2014-02-11 2016-04-12 Digimarc Corporation Methods, apparatus and arrangements for device to device communication
WO2015141939A1 (en) * 2014-03-21 2015-09-24 에스케이플래닛 주식회사 Method for providing additional service using lock screen mode, and system and apparatus for same
US10387004B2 (en) * 2014-04-17 2019-08-20 Jimmy Albert Real time monitoring of users within a predetermined range and selective receipt of virtual cards
JP6151214B2 (en) * 2014-04-28 2017-06-21 株式会社東芝 Electronics
CN107633397B (en) * 2014-05-29 2019-11-08 苹果公司 User interface for payment
US9967401B2 (en) 2014-05-30 2018-05-08 Apple Inc. User interface for phone call routing among devices
US10313506B2 (en) 2014-05-30 2019-06-04 Apple Inc. Wellness aggregator
US10430855B2 (en) * 2014-06-10 2019-10-01 Hussmann Corporation System, and methods for interaction with a retail environment
US10025963B2 (en) * 2014-06-30 2018-07-17 Symbol Technologies, Llc System for, and method of, detecting the presence of a mobile communication device in proximity to an imaging reader and for automatically configuring the reader to read an electronic code displayed on the device upon such detection
US10402896B1 (en) 2014-07-03 2019-09-03 Wells Fargo Bank, N.A. Systems and methods for interactive financial categorization and budgeting
US9477852B1 (en) * 2014-07-24 2016-10-25 Wells Fargo Bank, N.A. Augmented reality numberless transaction card
US9679152B1 (en) 2014-07-24 2017-06-13 Wells Fargo Bank, N.A. Augmented reality security access
US10223754B1 (en) 2014-08-12 2019-03-05 Wells Fargo Bank, N.A. Personal financial planning and engagement with peer-based comparison
US10339293B2 (en) 2014-08-15 2019-07-02 Apple Inc. Authenticated device used to unlock another device
US10452253B2 (en) 2014-08-15 2019-10-22 Apple Inc. Weather user interface
CN106797415A (en) 2014-09-02 2017-05-31 苹果公司 Telephone user interface
US10254948B2 (en) 2014-09-02 2019-04-09 Apple Inc. Reduced-size user interfaces for dynamically updated application overviews
KR20190101510A (en) 2014-09-02 2019-08-30 애플 인크. Reduced-size interfaces for managing alerts
US9547419B2 (en) 2014-09-02 2017-01-17 Apple Inc. Reduced size configuration interface
WO2016036413A1 (en) 2014-09-02 2016-03-10 Apple Inc. Multi-dimensional object rearrangement
US10262316B2 (en) 2014-09-23 2019-04-16 Sony Corporation Automatic notification of transaction by bank card to customer device
US9355424B2 (en) 2014-09-23 2016-05-31 Sony Corporation Analyzing hack attempts of E-cards
US9378502B2 (en) 2014-09-23 2016-06-28 Sony Corporation Using biometrics to recover password in customer mobile device
US9558488B2 (en) 2014-09-23 2017-01-31 Sony Corporation Customer's CE device interrogating customer's e-card for transaction information
US9292875B1 (en) 2014-09-23 2016-03-22 Sony Corporation Using CE device record of E-card transactions to reconcile bank record
US9646307B2 (en) 2014-09-23 2017-05-09 Sony Corporation Receiving fingerprints through touch screen of CE device
US9953323B2 (en) 2014-09-23 2018-04-24 Sony Corporation Limiting e-card transactions based on lack of proximity to associated CE device
US9367845B2 (en) 2014-09-23 2016-06-14 Sony Corporation Messaging customer mobile device when electronic bank card used
US9317847B2 (en) 2014-09-23 2016-04-19 Sony Corporation E-card transaction authorization based on geographic location
US9202212B1 (en) * 2014-09-23 2015-12-01 Sony Corporation Using mobile device to monitor for electronic bank card communication
US9299071B1 (en) * 2014-09-26 2016-03-29 Apriva, Llc System and method for processing a beacon based purchase transaction
CA2906911A1 (en) * 2014-09-29 2016-03-29 The Toronto-Dominion Bank Systems and methods for generating and administering mobile applications using pre-loaded tokens
US20160098699A1 (en) * 2014-10-07 2016-04-07 Mastercard International Incorporated User-friendly mobile payments system
DE102014015275A1 (en) * 2014-10-16 2016-04-21 Giesecke & Devrient Gmbh Data carrier with flat light source
JP5858305B1 (en) 2014-10-24 2016-02-10 アクアエンタープライズ株式会社 Mobile terminal, mobile terminal program, checkpoint management system, and checkpoint management method
US20160155160A1 (en) * 2014-12-01 2016-06-02 Comenity Llc Pre-populating a credit card number field
WO2016090140A1 (en) * 2014-12-04 2016-06-09 Mastercard International Incorporated Methods and apparatus for conducting secure magnetic stripe card transactions with a proximity payment device
US20160180319A1 (en) * 2014-12-22 2016-06-23 Apriva, Llc System and method for facilitating an online transaction with a mobile device
US10318955B2 (en) * 2014-12-23 2019-06-11 Paypal, Inc. Attribute based card combinations for digital wallets
KR20160090236A (en) * 2015-01-21 2016-07-29 삼성전자주식회사 Electronic device and transaction method using the same
CN107833045A (en) 2015-01-21 2018-03-23 三星电子株式会社 Electronic equipment and the method for commerce using electronic equipment
US10193700B2 (en) 2015-02-27 2019-01-29 Samsung Electronics Co., Ltd. Trust-zone-based end-to-end security
US10466883B2 (en) 2015-03-02 2019-11-05 Apple Inc. Screenreader user interface
US10055121B2 (en) 2015-03-07 2018-08-21 Apple Inc. Activity based thresholds and feedbacks
US10216351B2 (en) 2015-03-08 2019-02-26 Apple Inc. Device configuration user interface
US9779398B2 (en) * 2015-03-09 2017-10-03 Lenovo (Singapore) Pte. Ltd. Selecting a contactless payment card
US9916075B2 (en) 2015-06-05 2018-03-13 Apple Inc. Formatting content for a reduced-size user interface
KR20170011181A (en) * 2015-07-21 2017-02-02 엘지전자 주식회사 Mobile terminal and paying method using extended display and finger scan thereof
KR20170058134A (en) * 2015-11-18 2017-05-26 삼성전자주식회사 Method for providing user interface related to card and electronic device for the same
CN105740939B (en) * 2016-02-04 2019-06-11 中国计量学院 A kind of RFID label tag being integrated in PCBA
US9760773B1 (en) * 2016-06-01 2017-09-12 Wu-Hsu Lin Smart card with a retina identifying module
US10496973B2 (en) * 2016-07-29 2019-12-03 Square, Inc. Reprogrammable point-of-sale transaction flows
US10032169B2 (en) 2016-08-08 2018-07-24 Ellipse World, Inc. Prepaid, debit and credit card security code generation system
US9727759B1 (en) * 2016-08-08 2017-08-08 Ellipse World S.A. Prepaid, debit and credit card security code generation system
US10235674B2 (en) 2016-08-08 2019-03-19 Ellipse World, Inc. Method for a prepaid, debit and credit card security code generation system
US10075300B1 (en) * 2016-09-13 2018-09-11 Wells Fargo Bank, N.A. Secure digital communications
US10057061B1 (en) * 2016-09-13 2018-08-21 Wells Fargo Bank, N.A. Secure digital communications
US10373146B2 (en) 2016-12-29 2019-08-06 Capital One Services, Llc Smart card NFC secure money transfer
US10387632B2 (en) * 2017-05-17 2019-08-20 Bank Of America Corporation System for provisioning and allowing secure access to a virtual credential
US10298593B2 (en) * 2017-06-13 2019-05-21 Live Nation Entertainment, Inc. Systems and methods for big-data resource management
US10438032B1 (en) 2017-11-28 2019-10-08 Wells Fargo Bank, N.A. Data-securing chip card construction

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040127256A1 (en) * 2002-07-30 2004-07-01 Scott Goldthwaite Mobile device equipped with a contactless smart card reader/writer
US20070197261A1 (en) * 2004-03-19 2007-08-23 Humbel Roger M Mobile Telephone All In One Remote Key Or Software Regulating Card For Radio Bicycle Locks, Cars, Houses, And Rfid Tags, With Authorisation And Payment Function
US20080172317A1 (en) * 2007-01-09 2008-07-17 Doug Deibert Mobile phone payment with disabling feature
US20090143104A1 (en) * 2007-09-21 2009-06-04 Michael Loh Wireless smart card and integrated personal area network, near field communication and contactless payment system
US20120023024A1 (en) * 2010-07-26 2012-01-26 Graham Evans Programmable Card
US20120031969A1 (en) * 2009-05-15 2012-02-09 Ayman Hammad Integration of verification tokens with mobile communication devices
US20120150687A1 (en) * 2010-12-13 2012-06-14 Hart Annmarie D Systems and methods for conducting contactless payments using a mobile device and a magstripe payment card

Family Cites Families (59)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5960344A (en) * 1993-12-20 1999-09-28 Norand Corporation Local area network having multiple channel wireless access
US5748737A (en) * 1994-11-14 1998-05-05 Daggar; Robert N. Multimedia electronic wallet with generic card
US6353811B1 (en) * 1998-11-18 2002-03-05 Steven I. Weissman Credit card billing system for identifying expenditures on a credit card account
US6943678B2 (en) * 2000-01-24 2005-09-13 Nextreme, L.L.C. Thermoformed apparatus having a communications device
US7707120B2 (en) * 2002-04-17 2010-04-27 Visa International Service Association Mobile account authentication service
CN1894923A (en) * 2003-10-08 2007-01-10 史蒂芬·J·英格博格 Method and system for establishing a communication using privacy enhancing techniques
US7597250B2 (en) * 2003-11-17 2009-10-06 Dpd Patent Trust Ltd. RFID reader with multiple interfaces
US7693313B2 (en) * 2004-03-22 2010-04-06 Raytheon Company Personal authentication device
US8322624B2 (en) * 2007-04-10 2012-12-04 Feinics Amatech Teoranta Smart card with switchable matching antenna
US20060109119A1 (en) * 2004-11-19 2006-05-25 Jeremy Burr RFID tag in a printed circuit board
WO2006077942A1 (en) * 2005-01-19 2006-07-27 Brother Kogyo Kabushiki Kaisha Radio tag information management system, read device, tag label creation device, radio tag circuit element cartridge, and radio tag
US7124937B2 (en) * 2005-01-21 2006-10-24 Visa U.S.A. Inc. Wireless payment methods and systems
US7432816B1 (en) * 2005-10-13 2008-10-07 Hewlett-Packard Development Company, L.P. Printed circuit board with RFID antenna
JP5107934B2 (en) * 2005-12-21 2012-12-26 コーニンクレッカ フィリップス エレクトロニクス エヌ ヴィ Communication control method, RFID device, and RFID system
US8511547B2 (en) * 2005-12-22 2013-08-20 Mastercard International Incorporated Methods and systems for two-factor authentication using contactless chip cards or devices and mobile devices or dedicated personal readers
US20080074269A1 (en) * 2006-09-21 2008-03-27 Zih Corp. Rfid system and associated antenna-coupler
US7546671B2 (en) * 2006-09-26 2009-06-16 Micromechanic And Automation Technology Ltd. Method of forming an inlay substrate having an antenna wire
US20080094220A1 (en) * 2006-10-19 2008-04-24 Joseph Foley Methods and Systems for Improving RFID Security
US8390456B2 (en) * 2008-12-03 2013-03-05 Tego Inc. RFID tag facility with access to external devices
EP2122540A1 (en) * 2007-01-26 2009-11-25 LG Electronics Inc. Contactless interface within a terminal to support a contactless service
US8820638B1 (en) * 2007-07-27 2014-09-02 United Services Automobile Association (Usaa) System and methods related to an available balance debit/credit card
US20090069049A1 (en) * 2007-09-12 2009-03-12 Devicefidelity, Inc. Interfacing transaction cards with host devices
KR20090037797A (en) * 2007-10-12 2009-04-16 한국전자통신연구원 Tdma control method of mobile rfid reader via mobile phone base station
US8565723B2 (en) * 2007-10-17 2013-10-22 First Data Corporation Onetime passwords for mobile wallets
US8095113B2 (en) * 2007-10-17 2012-01-10 First Data Corporation Onetime passwords for smart chip cards
DE102007000589B9 (en) * 2007-10-29 2010-01-28 Bundesdruckerei Gmbh Method for protecting a chip card against unauthorized use, chip card and chip card terminal
US20090132362A1 (en) * 2007-11-21 2009-05-21 Mobile Candy Dish, Inc. Method and system for delivering information to a mobile communication device based on consumer transactions
US8352323B2 (en) * 2007-11-30 2013-01-08 Blaze Mobile, Inc. Conducting an online payment transaction using an NFC enabled mobile communication device
US10169692B2 (en) * 2007-12-24 2019-01-01 Dynamics Inc. Credit, security, debit cards and the like with buttons
US20090170559A1 (en) * 2007-12-27 2009-07-02 Simon Phillips Mobile telephone with two antennas for use in contactless payments
US8014720B2 (en) * 2007-12-31 2011-09-06 Intel Corporation Service provisioning utilizing near field communication
US9558485B2 (en) * 2008-01-30 2017-01-31 Paypal, Inc. Two step near field communication transactions
US9947002B2 (en) * 2008-02-15 2018-04-17 First Data Corporation Secure authorization of contactless transaction
US20090222383A1 (en) * 2008-03-03 2009-09-03 Broadcom Corporation Secure Financial Reader Architecture
US8174362B2 (en) * 2008-03-06 2012-05-08 Round Rock Research, Llc Methods and apparatuses to secure data transmission in RFID systems
US8031207B2 (en) * 2008-06-04 2011-10-04 Mastercard International, Inc. Card image description format to economize on data storage
US8662401B2 (en) * 2008-07-25 2014-03-04 First Data Corporation Mobile payment adoption by adding a dedicated payment button to mobile device form factors
KR101436608B1 (en) * 2008-07-28 2014-09-01 삼성전자 주식회사 Mobile terminal having touch screen and method for displaying cursor thereof
US8814052B2 (en) * 2008-08-20 2014-08-26 X-Card Holdings, Llc Secure smart card system
US20100078472A1 (en) 2008-09-30 2010-04-01 Apple Inc. Group peer-to-peer financial transactions
US20100082445A1 (en) * 2008-09-30 2010-04-01 Apple Inc. Smart menu options
US8040243B2 (en) * 2008-11-18 2011-10-18 The Boeing Company RFID-based corrosion and moisture detection
KR20100056159A (en) * 2008-11-19 2010-05-27 삼성전자주식회사 Radio frequency identification apparatus for applying a plurality of radio frequency identification schemes
DE102008060513A1 (en) * 2008-12-04 2010-06-17 Karsten Rackwitz Payment method for transmitting information between e.g. mobile telephones, using application software, involves allowing end user to enter amount of money to be transferred for mobile-based payment transaction
US9842356B2 (en) * 2008-12-17 2017-12-12 Iii Holdings 1, Llc System, method, apparatus and computer program product for interfacing a multi-card radio frequency (RF) device with a mobile communications device
US8579203B1 (en) * 2008-12-19 2013-11-12 Dynamics Inc. Electronic magnetic recorded media emulators in magnetic card devices
US9536238B2 (en) * 2008-12-31 2017-01-03 Peter Garrett Hand-held electronics device for aggregation of and management of personal electronic data
US8244181B2 (en) * 2009-05-26 2012-08-14 Qualcomm Incorporated Portable personal SIM card
US9135424B2 (en) * 2009-05-29 2015-09-15 Paypal, Inc. Secure identity binding (SIB)
US20100315678A1 (en) * 2009-06-16 2010-12-16 Thami Smires Method and apparatus of wirelessly connecting a first device to a second device
US8393545B1 (en) * 2009-06-23 2013-03-12 Dynamics Inc. Cards deployed with inactivated products for activation
US20110014084A1 (en) * 2009-07-20 2011-01-20 Eastern Alloys, Inc. High strength, creep resistant zinc alloy
US20110066550A1 (en) 2009-09-16 2011-03-17 Shank Clinton L System and method for a secure funds transfer
US8393546B1 (en) * 2009-10-25 2013-03-12 Dynamics Inc. Games, prizes, and entertainment for powered cards and devices
US8671055B2 (en) * 2010-03-02 2014-03-11 Digital Life Technologies, Llc Portable E-wallet and universal card
US9129270B2 (en) * 2010-03-02 2015-09-08 Gonow Technologies, Llc Portable E-wallet and universal card
SG183988A1 (en) * 2010-04-09 2012-10-30 Visa Int Service Ass System and method for securely validating transactions
US10223743B2 (en) * 2011-03-29 2019-03-05 Blackberry Limited Communication system providing near field communication (NFC) transaction features and related methods
US8918855B2 (en) * 2011-12-09 2014-12-23 Blackberry Limited Transaction provisioning for mobile wireless communications devices and related methods

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040127256A1 (en) * 2002-07-30 2004-07-01 Scott Goldthwaite Mobile device equipped with a contactless smart card reader/writer
US20070197261A1 (en) * 2004-03-19 2007-08-23 Humbel Roger M Mobile Telephone All In One Remote Key Or Software Regulating Card For Radio Bicycle Locks, Cars, Houses, And Rfid Tags, With Authorisation And Payment Function
US20080172317A1 (en) * 2007-01-09 2008-07-17 Doug Deibert Mobile phone payment with disabling feature
US20090143104A1 (en) * 2007-09-21 2009-06-04 Michael Loh Wireless smart card and integrated personal area network, near field communication and contactless payment system
US20120031969A1 (en) * 2009-05-15 2012-02-09 Ayman Hammad Integration of verification tokens with mobile communication devices
US20120023024A1 (en) * 2010-07-26 2012-01-26 Graham Evans Programmable Card
US20120150687A1 (en) * 2010-12-13 2012-06-14 Hart Annmarie D Systems and methods for conducting contactless payments using a mobile device and a magstripe payment card

Cited By (92)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150278800A1 (en) * 2006-09-24 2015-10-01 Rfcyber Corporation Method and apparatus for mobile payments
US10380573B2 (en) 2008-09-30 2019-08-13 Apple Inc. Peer-to-peer financial transaction devices and methods
US10296889B2 (en) 2008-09-30 2019-05-21 Apple Inc. Group peer-to-peer financial transactions
US9852368B1 (en) 2009-08-17 2017-12-26 Dynamics Inc. Advanced loyalty applications for powered cards and devices
US20150154581A1 (en) * 2009-10-13 2015-06-04 Square, Inc. Systems and methods for dynamic receipt generation with environmental information
US10482363B1 (en) 2010-03-02 2019-11-19 Dynamics Inc. Systems and methods for detection mechanisms for magnetic cards and devices
US10521180B1 (en) 2011-01-04 2019-12-31 AQ Corporation NFC-enabled apparatus and method of operation thereof
US20160062608A1 (en) * 2011-01-10 2016-03-03 Apple Inc. Button functionality
US10082892B2 (en) * 2011-01-10 2018-09-25 Apple Inc. Button functionality
US9349089B1 (en) 2011-05-23 2016-05-24 Dynamics Inc. Systems and methods for sensor mechanisms for magnetic cards and devices
US10142835B2 (en) 2011-09-29 2018-11-27 Apple Inc. Authentication with secondary approver
US10516997B2 (en) 2011-09-29 2019-12-24 Apple Inc. Authentication with secondary approver
US10484384B2 (en) 2011-09-29 2019-11-19 Apple Inc. Indirect authentication
US10419933B2 (en) 2011-09-29 2019-09-17 Apple Inc. Authentication with secondary approver
US9805364B2 (en) * 2011-10-12 2017-10-31 Technology Business Management Limited ID authentication
US20140330727A1 (en) * 2011-10-12 2014-11-06 Technology Business Management Limited ID Authentication
US9619741B1 (en) 2011-11-21 2017-04-11 Dynamics Inc. Systems and methods for synchronization mechanisms for magnetic cards and devices
US9317846B2 (en) * 2011-12-01 2016-04-19 At&T Intellectual Property I, L.P. Point of sale for mobile transactions
US9710745B1 (en) 2012-02-09 2017-07-18 Dynamics Inc. Systems and methods for automated assembly of dynamic magnetic stripe communications devices
US10395156B1 (en) 2012-05-15 2019-08-27 Dynamics Inc. Cards, devices, systems, methods and dynamic security codes
US20140025457A1 (en) * 2012-07-17 2014-01-23 Mastercard International Incorporated Method and system for deal redemption by electronic wallet
US20140108235A1 (en) * 2012-10-16 2014-04-17 American Express Travel Related Services Company, Inc. Systems and Methods for Payment Settlement
US9659246B1 (en) 2012-11-05 2017-05-23 Dynamics Inc. Dynamic magnetic stripe communications device with beveled magnetic material for magnetic cards and devices
US20140156517A1 (en) * 2012-11-30 2014-06-05 Wal-Mart Stores, Inc. Splitting a purchase among multiple parties using an electronic receipt after the transaction
US10108951B2 (en) 2012-11-30 2018-10-23 Walmart Apollo, Llc Splitting a purchase among multiple parties using an electronic receipt after the transaction
US9646750B1 (en) 2012-11-30 2017-05-09 Dynamics Inc. Dynamic magnetic stripe communications device with stepped magnetic material for magnetic cards and devices
US10311349B1 (en) 2012-11-30 2019-06-04 Dynamics Inc. Dynamic magnetic stripe communications device with stepped magnetic material for magnetic cards and devices
US10074082B2 (en) * 2012-11-30 2018-09-11 Walmart Apollo, Llc Splitting a purchase among multiple parties using an electronic receipt after the transaction
US20140222597A1 (en) * 2013-02-04 2014-08-07 Mastercard International Incorporated Intelligent mobile payment system and method
US20150206122A1 (en) * 2013-09-26 2015-07-23 Seth Daniel Elliott Point of sale normalization and extension services for invoice management
US9659296B2 (en) * 2013-12-18 2017-05-23 PayRange Inc. Method and system for presenting representations of payment accepting unit events
USD782483S1 (en) 2013-12-18 2017-03-28 Payrange, Inc. In-line dongle
USD755183S1 (en) 2013-12-18 2016-05-03 Payrange, Inc. In-line dongle
US20150170132A1 (en) * 2013-12-18 2015-06-18 PayRange Inc. Method and System for Presenting Representations of Payment Accepting Unit Events
US9875473B2 (en) 2013-12-18 2018-01-23 PayRange Inc. Method and system for retrofitting an offline-payment operated machine to accept electronic payments
US9256873B2 (en) 2013-12-18 2016-02-09 PayRange Inc. Method and device for retrofitting an offline-payment operated machine to accept electronic payments
US9547859B2 (en) 2013-12-18 2017-01-17 PayRange Inc. Method and system for performing mobile device-to-machine payments
USD782482S1 (en) 2013-12-18 2017-03-28 Payrange, Inc. In-line dongle
US10438208B2 (en) 2013-12-18 2019-10-08 PayRange Inc. Systems and methods for interacting with unattended machines using detectable trigger conditions and limited-scope authorization grants
US9134994B2 (en) 2013-12-18 2015-09-15 PayRange Inc. Method and system for updating firmware using a mobile device as a communications bridge
WO2015154552A1 (en) * 2014-04-10 2015-10-15 福建联迪商用设备有限公司 Sound-wave payment method and system
US9911123B2 (en) 2014-05-29 2018-03-06 Apple Inc. User interface for payments
US10438205B2 (en) 2014-05-29 2019-10-08 Apple Inc. User interface for payments
US10043185B2 (en) 2014-05-29 2018-08-07 Apple Inc. User interface for payments
US10482461B2 (en) 2014-05-29 2019-11-19 Apple Inc. User interface for payments
US10282727B2 (en) 2014-05-29 2019-05-07 Apple Inc. User interface for payments
US10066959B2 (en) 2014-09-02 2018-09-04 Apple Inc. User interactions for a mapping application
US10281999B2 (en) 2014-09-02 2019-05-07 Apple Inc. Button functionality
US9262771B1 (en) 2015-01-30 2016-02-16 PayRange Inc. Method and system for providing offers for automated retail machines via mobile devices
USD773508S1 (en) 2015-01-30 2016-12-06 PayRange Inc. Display screen or portion thereof with a graphical user interface
USD763905S1 (en) 2015-01-30 2016-08-16 PayRange Inc. Display screen or portion thereof with animated graphical user interface
USD862501S1 (en) 2015-01-30 2019-10-08 PayRange Inc. Display screen or portion thereof with a graphical user interface
USD764532S1 (en) 2015-01-30 2016-08-23 PayRange Inc. Display screen or portion thereof with animated graphical user interface
USD763888S1 (en) 2015-01-30 2016-08-16 PayRange Inc. Display screen or portion thereof with graphical user interface
USD836118S1 (en) 2015-01-30 2018-12-18 Payrange, Inc. Display screen or portion thereof with an animated graphical user interface
US10019724B2 (en) 2015-01-30 2018-07-10 PayRange Inc. Method and system for providing offers for automated retail machines via mobile devices
US10255595B2 (en) 2015-02-01 2019-04-09 Apple Inc. User interface for payments
US10024682B2 (en) 2015-02-13 2018-07-17 Apple Inc. Navigation user interface
US9940637B2 (en) 2015-06-05 2018-04-10 Apple Inc. User interface for loyalty accounts and private label accounts
US10332079B2 (en) 2015-06-05 2019-06-25 Apple Inc. User interface for loyalty accounts and private label accounts for a wearable device
US10026094B2 (en) 2015-06-05 2018-07-17 Apple Inc. User interface for loyalty accounts and private label accounts
US10467682B2 (en) 2015-12-07 2019-11-05 Mastercard International Incorporated Systems and methods for utilizing vehicle connectivity in association with payment transactions
US10424007B2 (en) 2015-12-07 2019-09-24 Mastercard International Incorporated Systems and methods for utilizing vehicle connectivity in association with payment transactions
US9965911B2 (en) 2015-12-07 2018-05-08 Capital One Services, Llc Electronic access control system
US10360747B2 (en) 2015-12-07 2019-07-23 Capital One Services, Llc Electronic access control system
US10410200B2 (en) 2016-03-15 2019-09-10 Square, Inc. Cloud-based generation of receipts using transaction information
US10334054B2 (en) 2016-05-19 2019-06-25 Apple Inc. User interface for a device requesting remote authorization
US9847999B2 (en) 2016-05-19 2017-12-19 Apple Inc. User interface for a device requesting remote authorization
WO2017213785A1 (en) * 2016-06-11 2017-12-14 Apple Inc. User interface for transaction
US9842330B1 (en) 2016-09-06 2017-12-12 Apple Inc. User interfaces for stored-value accounts
US10496808B2 (en) 2016-10-25 2019-12-03 Apple Inc. User interface for managing access to credentials for use in an operation
WO2018200121A1 (en) * 2017-04-24 2018-11-01 Mastercard International Incorporated A digital wallet payment system and process
US10395128B2 (en) 2017-09-09 2019-08-27 Apple Inc. Implementation of biometric authentication
US10410076B2 (en) 2017-09-09 2019-09-10 Apple Inc. Implementation of biometric authentication
US10521579B2 (en) 2017-09-09 2019-12-31 Apple Inc. Implementation of biometric authentication
US10536414B2 (en) 2018-08-22 2020-01-14 Apple Inc. Electronic message user interface
US10511443B1 (en) 2018-10-02 2019-12-17 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10489781B1 (en) 2018-10-02 2019-11-26 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10505738B1 (en) 2018-10-02 2019-12-10 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10467622B1 (en) 2019-02-01 2019-11-05 Capital One Services, Llc Using on-demand applications to generate virtual numbers for a contactless card to securely autofill forms
US10510074B1 (en) 2019-02-01 2019-12-17 Capital One Services, Llc One-tap payment using a contactless card
US10339530B1 (en) 2019-02-21 2019-07-02 Capital One Services, Llc Touch authentication of multiple users or operating modes for a transaction card
US10425129B1 (en) 2019-02-27 2019-09-24 Capital One Services, Llc Techniques to reduce power consumption in near field communication systems
US10542036B1 (en) 2019-03-12 2020-01-21 Capital One Services, Llc Systems and methods for signaling an attack on contactless cards
US10523708B1 (en) 2019-03-18 2019-12-31 Capital One Services, Llc System and method for second factor authentication of customer support calls
US10438437B1 (en) 2019-03-20 2019-10-08 Capital One Services, Llc Tap to copy data to clipboard via NFC
US10535062B1 (en) 2019-03-20 2020-01-14 Capital One Services, Llc Using a contactless card to securely share personal data stored in a blockchain
US10467445B1 (en) 2019-03-28 2019-11-05 Capital One Services, Llc Devices and methods for contactless card alignment with a foldable mobile device
US10516447B1 (en) 2019-06-17 2019-12-24 Capital One Services, Llc Dynamic power levels in NFC card communications
US10498401B1 (en) 2019-07-15 2019-12-03 Capital One Services, Llc System and method for guiding card positioning using phone sensors
US10506426B1 (en) 2019-07-19 2019-12-10 Capital One Services, Llc Techniques for call authentication
US10541995B1 (en) 2019-07-23 2020-01-21 Capital One Services, Llc First factor contactless card authentication system and method

Also Published As

Publication number Publication date
EP2707847A4 (en) 2015-04-01
WO2012154915A1 (en) 2012-11-15
US20120286936A1 (en) 2012-11-15
EP2707847A1 (en) 2014-03-19
US20120290449A1 (en) 2012-11-15
CA2835508A1 (en) 2012-11-15
US20120286928A1 (en) 2012-11-15

Similar Documents

Publication Publication Date Title
US8639629B1 (en) System and method for accessing an online user account registry via a thin-client unique user code
US8660948B2 (en) System and method for managing transactions with a portable computing device
US8255323B1 (en) Motion based payment confirmation
US9448698B2 (en) Free-form entries during payment processes
JP6214535B2 (en) System and method of media distribution service platform for mobile offer bumping
US9483763B2 (en) User interface for payments
AU2007339930B2 (en) Real-time balance updates
US9047600B2 (en) Mobile and wearable device payments via free cross-platform messaging service, free voice over internet protocol communication, free over-the-top content communication, and universal digital mobile and wearable device currency faces
US9208482B2 (en) Transaction token issuing authorities
AU2007339916B2 (en) Mobile coupon method and portable consumer device for utilizing same
US8985442B1 (en) One-touch payment using haptic control via a messaging and calling multimedia system on mobile device and wearable device, currency token interface, point of sale device, and electronic payment card
US9940627B2 (en) Mobile coupon method and system
US8478232B2 (en) Prepaid text messaging service
CA2795766C (en) Mobile phone payment processing methods and systems
US20140032381A1 (en) Payment services provider methods in connection with personalized payments system
JP2007310889A (en) Radio frequency identification purchase transactions
US10242326B2 (en) Mobile commercial systems and methods
US9881293B2 (en) Electronic receipt system
US8862513B2 (en) Mobile barcode generation and payment
US10510056B2 (en) Method and system for multiple payment applications
US20100125495A1 (en) System and method of providing a mobile wallet at a mobile telephone
US9117210B2 (en) Systems and methods for randomized mobile payment
CN105474224B (en) Security platform system and correlation technique, device and electronic equipment
US20130046645A1 (en) System and method for point of transaction authentication
US9842356B2 (en) System, method, apparatus and computer program product for interfacing a multi-card radio frequency (RF) device with a mobile communications device

Legal Events

Date Code Title Description
AS Assignment

Owner name: DYNAMICS INC., PENNSYLVANIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:WALLACE, MICHAEL T.;REEL/FRAME:028188/0997

Effective date: 20120510

AS Assignment

Owner name: DYNAMICS INC., PENNSYLVANIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MULLEN, JEFFREY D.;RIGATTI, CHRISTOPHER J.;SIGNING DATES FROM 20120516 TO 20120517;REEL/FRAME:028346/0921

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STCB Information on status: application discontinuation

Free format text: FINAL REJECTION MAILED