US20140025457A1 - Method and system for deal redemption by electronic wallet - Google Patents

Method and system for deal redemption by electronic wallet Download PDF

Info

Publication number
US20140025457A1
US20140025457A1 US13/551,124 US201213551124A US2014025457A1 US 20140025457 A1 US20140025457 A1 US 20140025457A1 US 201213551124 A US201213551124 A US 201213551124A US 2014025457 A1 US2014025457 A1 US 2014025457A1
Authority
US
United States
Prior art keywords
deal
financial transaction
transaction
mobile device
wallet identifier
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.)
Abandoned
Application number
US13/551,124
Inventor
Jose-Luis Celorio Martinez
Andrea Christine GILMAN
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.)
Mastercard International Inc
Original Assignee
Mastercard International 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
Application filed by Mastercard International Inc filed Critical Mastercard International Inc
Priority to US13/551,124 priority Critical patent/US20140025457A1/en
Assigned to MASTERCARD INTERNATIONAL INCORPORATED reassignment MASTERCARD INTERNATIONAL INCORPORATED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: GILMAN, ANDREA CHRISTINE, MARTINEZ, JOSE-LUIS CELORIO
Priority to PCT/US2013/050841 priority patent/WO2014015010A1/en
Publication of US20140025457A1 publication Critical patent/US20140025457A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/20Point-of-sale [POS] network systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/327Short range or proximity payments by means of M-devices
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/327Short range or proximity payments by means of M-devices
    • G06Q20/3274Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being displayed on the M-device
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices or networks 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 OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/387Payment using discounts or coupons
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • G06Q30/0207Discounts or incentives, e.g. coupons or rebates
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/06Buying, selling or leasing transactions

Definitions

  • the present disclosure relates to the redemption of daily deals using an electronic wallet, specifically the selection of a deal and payment card to be applied to a transaction on a mobile device and then the initiation of the financial transaction by that mobile device or a merchant point-of-sale.
  • the present disclosure provides a description of a systems and methods for redemption of a deal using an electronic wallet by initiating a financial transaction on a mobile device or a merchant point-of-sale.
  • a method for initiating a financial transaction on a mobile device includes: transmitting, by a transmitter of the mobile device, a wallet identifier associated with the mobile device; receiving, by a receiver of a mobile device, transaction information for a financial transaction to be initiated, wherein the transaction information includes at least a transaction amount; storing, in a database, at least one deal and a payment card, wherein each deal of the at least one deal includes at least a discount amount; receiving, via an input of the mobile device, an indication of a deal of the at least one deal to be applied to the financial transaction to be initiated; and initiating, by a processor of the mobile device, a financial transaction using the payment card by transmitting, via the transmitter, an authorization request for the financial transaction, wherein the authorization request includes the payment card and is for a remaining amount, and wherein the remaining amount is based on the transaction amount and the discount amount corresponding to the indicated deal.
  • a method for initiating a financial transaction includes: identifying, by a processing device, a transaction amount for a financial transaction to be initiated; receiving, from a receiving device, a wallet identifier associated with a mobile device; transmitting, to a server, at least the transaction amount and the wallet identifier; receiving, from the server, deal information corresponding to a deal to be applied to the financial transaction to be initiated, wherein the deal information includes at least a discount amount; initiating, by a processing device, a financial transaction by transmitting, via a transmitting device, an authorization request for the financial transaction, wherein the authorization request is for a remaining amount, and wherein the remaining amount is based on the transaction amount and the discount amount corresponding to the deal.
  • a mobile device for initiating a financial transaction includes a transmitting device, a receiving device, a database, an input device, and a processor.
  • the transmitting device is configured to transmit a wallet identifier associated with the mobile device.
  • the receiving device is configured to receive transaction information for a financial transaction to be initiated, wherein the transaction information includes at least a transaction amount.
  • the database is configured to store at least one deal and a payment card, wherein each deal of the at least one deal includes at least a discount amount.
  • the input device is configured to read an indication of a deal of the at least one deal to be applied to the financial transaction to be initiated.
  • the processor is configured to initiate a financial transaction using the payment card by transmitting, via the transmitter, an authorization request for the financial transaction, wherein the authorization request includes the payment card and is for a remaining amount, and wherein the remaining amount is based on the transaction amount and the discount amount corresponding to the indicated deal.
  • a system for initiating a financial transaction includes a processing device, a receiving device, and a transmitting device.
  • the processing device is configured to identify a transaction amount for a financial transaction to be initiated.
  • the receiving device is configured to receive a wallet identifier associated with a mobile device.
  • the transmitting device is configured to transmit, to a server, at least the transaction amount and the wallet identifier.
  • the receiving device is further configured to receive, from the server, deal information corresponding to a deal to be applied to the financial transaction to be initiated, wherein the deal information includes at least a discount amount.
  • the processing device is further configured to initiate a financial transaction by causing the transmitting device to transmit an authorization request for the financial transaction, and wherein the authorization request is for a remaining amount, and the remaining amount is based on the transaction amount and the discount amount corresponding to the deal.
  • FIG. 1 is a block diagram illustrating a system for redeeming a deal and initiating a financial transaction with an electronic wallet in accordance with exemplary embodiments.
  • FIG. 2 is a block diagram illustrating a mobile device in accordance with exemplary embodiments.
  • FIG. 3 is a block diagram illustrating the merchant of FIG. 1 in accordance with exemplary embodiments.
  • FIGS. 4A and 4B are diagrams illustrating a graphical user interface for applying a deal and initiating a financial transaction using an electronic wallet in accordance with exemplary embodiments.
  • FIGS. 5A and 5B are diagrams illustrating graphical user interfaces for transmitting wallet identifiers to a merchant receiving device in accordance with exemplary embodiments.
  • FIGS. 6A and 6B are flow diagrams illustrating a method for initiating a financial transaction using an electronic wallet of a mobile device in accordance with exemplary embodiments.
  • FIGS. 7A and 7B are flow diagrams illustrating a method for initiating a financial transaction using an electronic wallet via a merchant point-of-sale in accordance with exemplary embodiments.
  • FIG. 8 is a block diagram illustrating system architecture of a computer system in accordance with exemplary embodiments.
  • FIGS. 9 and 10 are flow charts illustrating exemplary methods for initiating a financial transaction in accordance with exemplary embodiments.
  • An electronic wallet may be a mobile application capable of being stored on and/or executed on a mobile device, such as a smart phone.
  • the electronic wallet may be stored in a memory device located in the mobile device.
  • An electronic wallet may allow a user of the mobile device to enable payment of a financial transaction across multiple channels of commerce by utilizing the electronic wallet application on the mobile device.
  • the electronic wallet may utilize existing payment networks (e.g., operated by MasterCard, VISA, etc.) which are already accepted by merchants, thereby eliminating the need for heavy integration, while providing more security and better economics.
  • Electronic wallets may function with existing authorization techniques (e.g., personal identification numbers, etc.) and not require modification of existing systems. Additional information regarding methods for implementing and using electronic wallets on a mobile device, including the storage and transmission of payment details for financial transactions, can be found in U.S. patent application Ser. No. 13/209,312, filed Aug. 12, 2011, entitled “Mutli-Commerce Channel Wallet for Authenticated Transactions”; U.S. Provisional Patent Application No. 61/605,588, filed Mar.
  • FIG. 1 illustrates a system 100 for applying a deal using an electronic wallet of a mobile device and initiating a financial transaction using the electronic wallet, or, alternatively, a merchant point of sale.
  • the system 100 may include a mobile device 102 .
  • the mobile device 102 may be any type of mobile device suitable for performing the functions as disclosed herein, such as a smart phone, as will be apparent to persons having skill in the relevant art.
  • the mobile device 102 may include an electronic wallet application.
  • the mobile device 102 may include a deal database 104 .
  • the deal database 104 may be configured to store at least one deal.
  • a deal may be a promotional value that may be applied to a financial transaction with a merchant, such as a discount, a coupon, an offer, etc.
  • a deal may be a discount for a specific product (e.g., $1 off the product) or a stored value for a pre-purchased deal (e.g., user pays $20 to receive $40 worth of goods or services), a discount for a transaction ($10 off any purchase), may be tied to a specific merchant, may require a minimum purchase, etc.
  • Types of deals and offers that may be used in the systems and methods as disclosed herein will be apparent to persons having skill in the relevant art.
  • Each deal in the deal database 104 may include at least a discount amount.
  • each deal may also include a deal identifier (e.g., for tracking redemption of the deal).
  • the deal database 104 may be included as part of the electronic wallet, may be included as part of the mobile device 102 but not as part of the electronic wallet, or may be external to the mobile device 102 and accessed via a network (e.g., a network 110 , discussed in more detail below).
  • the deal database 104 may be included as part of a financial transaction processing agency.
  • the deal database 104 may be a single database or may include multiple databases interfaced together (e.g., physically, or via a network, such as the network 110 ). Suitable types and configurations of the deal database 104 will be apparent to persons having skill in the relevant art.
  • a user of the mobile device 102 may visit a location (e.g., physical, virtual, etc.) of a merchant 106 to conduct a financial transaction.
  • the merchant 106 may ring up products (e.g., goods or services) for purchase by a user of the mobile device 102 .
  • the user may indicate that they wish to apply a deal to the transaction.
  • the user or the mobile device 102 may provide a wallet identifier to the merchant 106 , which may be entered by the merchant 106 into the transaction (e.g., using the point-of-sale device).
  • the merchant 106 may obtain the wallet identifier by transmission of the wallet identifier by the mobile device 102 to a point-of-sale or other device of the merchant 106 .
  • the mobile device 102 may transmit the wallet identifier to the merchant 106 via near field communication, the mobile device 102 may display a machine-readable code (e.g., a QR code) encoded with the wallet identifier to be read by the merchant 106 , etc.
  • a machine-readable code e.g., a QR code
  • Methods of transmitting the wallet identifier to the merchant 106 will be apparent to persons having skill in the relevant art.
  • the merchant 106 may receive the wallet identifier by reading magnetic media encoded with the wallet identifier, such as the magnetic strip on a payment card (e.g., for which the user of the mobile device 102 is the cardholder). It will be apparent to persons having skill in the relevant art that reading information (e.g., the wallet identifier) encoded in a payment card may be performed without using a financial transaction processing network and may be done using existing point-of-sale systems.
  • the wallet identifier may be a unique value associated with the mobile device 102 , such as a unique number (e.g., a Media Access Control number, phone number, etc.), an e-mail address, a name, or any other value that may be uniquely associated with the mobile device 102 .
  • the merchant 106 may transmit purchase details for the potential transaction to a financial transaction processing server 108 .
  • the purchase details may include at least the amount of the transaction, the wallet identifier, and a merchant identifier associated with the merchant 106 .
  • the financial transaction processing server 108 may, using the wallet identifier, push at least the amount of the transaction to the mobile device 102 .
  • the mobile device 102 may display (e.g., via the electronic wallet application) the transaction to the user and the user may indicate a deal from the deal database 104 to be applied to the transaction.
  • the electronic wallet may automatically display only those deals that would be valid for the present transaction (e.g., based on the merchant 106 , the transaction amount, etc.).
  • the information transmitting by the financial transaction processing server 108 may include information indicating only those deals that may be valid for the present transaction.
  • the electronic wallet may apply the deal to the transaction (e.g., and reducing the transaction amount based on the discount amount corresponding to the deal) and may prompt the user to select a payment card.
  • the user may select a payment card and the mobile device 102 may initiate a financial transaction for the reduced transaction amount using the selected payment card by submitting an authorization request to the financial transaction processing server 108 .
  • the financial transaction processing server 108 may, using the wallet identifier, transmit deal information corresponding to a deal to be applied to the transaction to the merchant 106 .
  • the deal information may include at least a discount amount (e.g., $10, 10%, etc.) for the corresponding deal.
  • the merchant 106 may calculate a remaining amount for the transaction by applying the discount amount to the transaction amount, and may initiate a financial transaction for the remaining amount by submitting an authorization request to the financial transaction processing server 108 . It will be apparent to persons having skill in the relevant art that, in this embodiment, the merchant 106 may obtain payment information from the electronic wallet of the mobile device 102 at multiple steps in the process.
  • the merchant 106 may obtain payment details prior to obtaining the wallet identifier, at the same time as obtaining the wallet identifier (e.g., using near field communication), or after applying the deal to the transaction but prior to submitting the authorization request.
  • Methods for transmitting and/or receiving payment details using an electronic wallet will be apparent to persons having skill in the relevant art.
  • the financial transaction processing server 108 may receive the authorization request and may, using methods apparent to those having skill in the relevant art, process the financial transaction for the reduced amount and using the selected payment card. For example, the financial transaction processing server 108 may process the financial transaction using a traditional four party system (e.g., consumer, merchant, acquirer, and issuer). The financial transaction processing server 108 may notify the merchant 106 (e.g., and the mobile device 102 ) of a response to the authorization request. The merchant 106 may then finalize the transaction (e.g., by providing the goods and/or services to the user of the mobile device 102 ).
  • a traditional four party system e.g., consumer, merchant, acquirer, and issuer.
  • the financial transaction processing server 108 may notify the merchant 106 (e.g., and the mobile device 102 ) of a response to the authorization request.
  • the merchant 106 may then finalize the transaction (e.g., by providing the goods and/or services to the user of the mobile device 102 ).
  • the network 110 may be any network suitable for performing the functions as disclosed herein and may include a local area network (LAN), a wide area network (WAN), a wireless network (e.g., WiFi), a mobile communication network, a satellite network, the Internet, fiber optic, coaxial cable, infrared, radio frequency (RF), or any combination thereof.
  • LAN local area network
  • WAN wide area network
  • WiFi wireless network
  • RF radio frequency
  • FIG. 2 illustrates a block diagram of the mobile device 102 .
  • the mobile device 102 may include the deal database 104 , a transmitting unit 202 , a receiving unit 204 , a processing unit 206 , a display unit 208 , and an input unit 210 .
  • Each of the components may be connected via a bus 212 . Suitable types and configurations of the bus 212 will be apparent to persons having skill in the relevant art.
  • the transmitting unit 202 may be configured to transmit the wallet identifier associated with the mobile device 102 (e.g., to the financial transaction processing server 108 and/or the merchant 106 ). In one embodiment, the transmitting unit 202 may be configured to transmit the wallet identifier via near field communication.
  • the receiving unit 204 may be configured to receive (e.g., from the financial transaction processing server 108 ) purchase details for a transaction. The purchase details may include at least the transaction amount, but may also include the merchant identifier, product information, etc.
  • the display unit 208 may be configured to display the received purchase details and at least one deal included in the deal database 104 to the user.
  • the display unit 208 may be any type of display suitable for display information to a user of the mobile device, such as a liquid crystal display (LCD), a light-emitting diode (LED) display, a capacitive touch display, etc.
  • the processing unit 206 may be configured to identify only deals in the deal database 104 that are valid for application for the purchase.
  • the purchase details may include deals valid for application for the purchase (e.g., as identified by the financial transaction processing server 108 ).
  • the display unit 208 may be configured to display a machine readable code (e.g., a bar code, such as a QR code) encoded with the wallet identifier (e.g., to transmit the wallet identifier to the merchant 106 ).
  • a machine readable code e.g., a bar code, such as a QR code
  • the input unit 210 may be configured to receive input from a user indicating a deal to be applied to the transaction.
  • the input unit 210 may be any input device suitable for performing the functions as disclosed herein, such as a keyboard, a capacitive touch display, etc.
  • the processing unit 206 may identify the discount amount corresponding to the indicated deal, and may identify a reduced amount based on the transaction amount and the discount amount.
  • the display unit 208 may be configured to display the reduced amount to the user of the mobile device 102 .
  • the input unit 210 may be further configured to receive input from a user indicating a payment card to be used for the transaction.
  • the processing unit 206 may be configured to cause the transmitting unit 202 to transmit an authorization request for a financial transaction (e.g., to the financial transaction processing server 108 ).
  • the authorization request may include the payment card and may be for the reduced amount.
  • FIG. 3 illustrates a block diagram of the merchant 106 .
  • the merchant 106 may include a processing unit 302 , a receiving unit 304 , a transmitting unit 306 , a display unit 308 , and an input unit 310 .
  • Each of the components may be connected via a bus 312 . Suitable types and configurations of the bus 312 will be apparent to persons having skill in the relevant art.
  • the processing unit 302 may be configured to identify a transaction amount for a financial transaction to be initiated (e.g., such as through ringing up items at the merchant 106 point-of-sale).
  • the receiving unit 304 may be configured to receive a wallet identifier associated with a mobile device (e.g., the mobile device 102 ).
  • the receiving unit 304 may receive the wallet identifier using near field communication, by reading a machine readable code (e.g., a QR code) or magnetic media encoded with the wallet identifier, etc.
  • the transmitting unit 306 may be configured to transmit the identified transaction amount and received wallet identifier to a server (e.g., the financial transaction processing server 108 ).
  • the receiving unit 304 may be further configured to receive (e.g., from the financial transaction processing server 108 ), deal information corresponding to a deal to be applied to the financial transaction to be initiated.
  • the deal information may include at least a discount amount for the corresponding deal.
  • the processing unit 302 may be configured to apply the discount amount to the transaction amount to obtain a remaining amount for the financial transaction to be initiated.
  • the processing unit 302 may then initiate a financial transaction by causing the transmitting unit 306 to transmit an authorization request for the financial transaction to the financial transaction processing server 108 .
  • FIGS. 4A and 4B illustrate a graphical user interface of the mobile device 102 for the indication of a deal and a payment card for initiating a financial transaction.
  • a display 402 of the mobile device 102 may display the electronic wallet application.
  • the application may display a transaction amount 404 , which may be received from the financial transaction processing server 108 .
  • the application may also display at least one deal 406 that may be applied to the transaction.
  • Each deal displayed may also include a discount amount 408 and a button 410 .
  • the user may interact with the button 410 (e.g., via the input unit 210 ) to indicate the corresponding deal 406 to be applied to the transaction.
  • the processing unit 206 may then apply the deal 406 to the transaction as discussed herein.
  • the display 402 may display a graphical user interface as illustrated in FIG. 4B .
  • the display 402 may display to the user of the mobile device 102 the transaction amount 404 , the discount amount 408 of the indicated deal 406 , and a reduced amount 412 .
  • the electronic wallet application may also display at least one payment card 414 for use in paying for the transaction.
  • the display of the payment card 414 may include a card identifier 416 .
  • the card identifier 416 may include a commercial name for the card, the issuer of the payment card, the payment card number (e.g., which may be partially obscured as illustrated in FIG. 4B ), or a customized name or display as selected by the user of the mobile device 102 .
  • the payment card 414 may also include a button 418 .
  • the user may interact with the button 418 to indicate the payment card 414 for payment.
  • the mobile device 102 may then initiate a financial transaction by transmitting an authorization request to the financial transaction processing server 108 .
  • the authorization request may include at least the reduced amount 412 and the payment card 414 to be charged in the transaction.
  • the display 402 may display a confirmation message to the user once the authorization request has been transmitted and/or a confirmation message may be transmitted to the mobile device 102 (e.g., via electronic mail, short message service, etc.).
  • FIGS. 5A and 5B illustrate graphical user interfaces for the mobile device 102 for the transmitting of the wallet identifier to the merchant 106 (e.g., for initiation of the financial transaction by the merchant 106 point-of-sale).
  • the display 402 of the mobile device 102 may display a machine readable code 502 .
  • the machine readable code 502 may be encoded with at least the wallet identifier.
  • the machine readable code 502 may be a bar code or any other type of machine readable code suitable for the transmission of the wallet identifier to the merchant 106 , such as a QR code as illustrated in FIG. 5A .
  • the display 402 of the mobile device 102 may display a notification message 504 .
  • the notification message 504 may indicate to the user of the mobile device 102 that the mobile device 102 is currently transmitting (e.g., via the transmitting unit 202 ) the wallet identifier via near field communication.
  • the display 402 may also display payment card information for the user to indicate a payment card to be transmitted to the merchant 106 in addition to the wallet identifier.
  • the display 402 may display the payment card 414 as illustrated in FIG. 4B .
  • the user of the mobile device 102 may select the payment card 414 using the wallet application prior to the transmission of information via near field communication, such as indicated in the notification message 504 of FIG. 5B .
  • FIGS. 6A and 6B are a flow diagram illustrating a method for redeeming a deal using an electronic wallet and initiating a financial transaction.
  • the merchant 106 may ring up a purchase for a user of the mobile device 102 at the point-of-sale.
  • the merchant 106 may enter the wallet identifier associated with the mobile device 102 into the point-of-sale.
  • the merchant 106 may manually enter the wallet identifier.
  • the merchant 106 may use a reader device to read a machine-readable code displayed by the mobile device 102 encoded with the wallet identifier.
  • the machine-readable code may be a QR code.
  • the mobile device 102 may transmit the wallet identifier to the merchant 106 point-of-sale using near field communication.
  • the merchant 106 may transmit purchase details to the financial transaction processing server 108 , who may receive the purchase details in step 608 .
  • the purchase details may include at least the transaction amount, the wallet identifier, and a merchant identifier associated with the merchant 106 .
  • the financial transaction processing server 108 may identify the mobile device 102 based on the wallet identifier and may push (e.g., transmit) the purchase details to the mobile device 102 .
  • the mobile device 102 may receive (e.g., via the receiving unit 204 ) the purchase details and may display them (e.g., via the display unit 208 ) to the user.
  • the mobile device 102 may also receive from the financial transaction processing server 108 information identifying deals (e.g., stored in the deal database 104 ) that are valid for applying to the financial transaction to be initiated. In a further embodiment, the mobile device 102 may display only those deals identified as being valid for the financial transaction.
  • deals e.g., stored in the deal database 104
  • the mobile device 102 may receive an indication (e.g., via the input unit 210 ) of a deal (e.g., stored in the deal database 104 ) to be applied to the purchase and may apply the deal. Application of the deal to the purchase may include identifying (e.g., calculating) a reduced transaction amount based on the transaction amount and a discount amount corresponding to the indicated deal.
  • the mobile device 102 may receive an indication of a payment card to be applied to the purchase. Using the indicated payment card, the mobile device 102 may then, in step 618 , initiate a financial transaction by transmitting an authorization request.
  • the authorization request may include at least the reduced transaction amount and the payment card.
  • the financial transaction processing server 108 may receive the authorization request for the initiated financial transaction.
  • the financial transaction processing server 108 may process the financial transaction. Methods for processing a financial transaction will be apparent to persons having skill in the relevant art.
  • the financial transaction processing server 108 may transmit an authorization response (e.g., indicating approval or denial of the transaction) to the merchant 106 .
  • the merchant 106 may receive the authorization response and, in step 626 , may finalize the transaction accordingly.
  • the financial transaction processing server 108 may also transmit a notification of the processing of the financial transaction to the mobile device 102 (e.g., for display via the display unit 208 ).
  • FIGS. 7A and 7B are a flow diagram illustrating a method for redeeming a deal of an electronic wallet of a mobile device and initiating a financial transaction via a merchant point-of-sale.
  • the merchant 106 may ring up a purchase for a user of the mobile device 102 at the point-of-sale and identify a transaction amount for the purchase. In some embodiments, the merchant 106 may obtain payment details regarding payment for the financial transaction during step 702 .
  • the mobile device 102 may transmit the wallet identifier to the merchant 106 . In one embodiment, the mobile device 102 may transmit the wallet identifier using near field communication. In another embodiment, the wallet identifier may be transmitted by display a machine readable code encoded with the wallet identifier on the mobile device 102 . In a further embodiment, the machine readable code may be a bar code. In one embodiment, the bar code may be a QR code. In some embodiments, the mobile device 102 may also transmit payment details in addition to the wallet identifier.
  • the merchant 106 may receive the wallet identifier. Then, in step 708 , the merchant 106 may transmit purchase details to the financial transaction processing server 108 .
  • the purchase details may include at least the identified transaction amount and the received wallet identifier.
  • the financial transaction processing server 108 may receive the purchase details in step 710 , and then, in step 712 , may identify a deal to be applied to the transaction and push corresponding deal information to the merchant 106 .
  • the deal information may include at least a discount amount of the corresponding deal. In one embodiment the discount amount may be an integer (e.g., $10 off) or a percent (e.g., 10% off).
  • the merchant 106 may receive the deal information, and then may apply the deal to the purchase in step 716 .
  • the merchant 106 may calculate, in step 718 , a remaining amount for the purchase. In one embodiment, the remaining amount may be calculated by reducing the transaction amount based on the discount amount of the corresponding deal.
  • the merchant 106 may initiate a financial transaction by submitting an authorization request to the financial transaction processing server 108 for the remaining transaction amount.
  • the financial transaction processing server 108 may receive the authorization request for the initiated financial transaction.
  • the financial transaction processing server 108 may process the financial transaction. Methods for processing a financial transaction will be apparent to persons having skill in the relevant art.
  • the financial transaction processing server 108 may transmit an authorization response (e.g., indicating approval or denial of the transaction) to the merchant 106 .
  • the merchant 106 may receive the authorization response and, in step 728 , may finalize the transaction accordingly.
  • the financial transaction processing server 108 may also transmit a notification of the processing of the financial transaction to the mobile device 102 (e.g., for display via the display unit 208 ).
  • FIG. 8 illustrates a computer system 800 in which embodiments of the present disclosure, or portions thereof, may be implemented as computer-readable code.
  • the deal provider 104 , the merchant 106 , and the financial transaction processing agency 110 of FIG. 1 may be implemented in the computer system 800 using hardware, software, firmware, non-transitory computer readable media having instructions stored thereon, or a combination thereof and may be implemented in one or more computer systems or other processing systems.
  • Hardware, software, or any combination thereof may embody modules and components used to implement the methods of FIGS. 6A , 6 B, 7 A, 7 B, 9 , and 10 .
  • programmable logic may execute on a commercially available processing platform or a special purpose device.
  • a person having ordinary skill in the art may appreciate that embodiments of the disclosed subject matter can be practiced with various computer system configurations, including multi-core multiprocessor systems, minicomputers, mainframe computers, computers linked or clustered with distributed functions, as well as pervasive or miniature computers that may be embedded into virtually any device.
  • processor device and a memory may be used to implement the above described embodiments.
  • a processor device as discussed herein may be a single processor, a plurality of processors, or combinations thereof. Processor devices may have one or more processor “cores.”
  • the terms “computer program medium,” “non-transitory computer readable medium,” and “computer usable medium” as discussed herein are used to generally refer to tangible media such as a removable storage unit 818 , a removable storage unit 822 , and a hard disk installed in hard disk drive 812 .
  • Processor device 804 may be a special purpose or a general purpose processor device.
  • the processor device 804 may be connected to a communication infrastructure 806 , such as a bus, message queue, network (e.g., the network 110 ), multi-core message-passing scheme, etc.
  • the computer system 800 may also include a main memory 508 (e.g., random access memory, read-only memory, etc.), and may also include a secondary memory 810 .
  • the secondary memory 810 may include the hard disk drive 812 and a removable storage drive 814 , such as a floppy disk drive, a magnetic tape drive, an optical disk drive, a flash memory, etc.
  • the removable storage drive 814 may read from and/or write to the removable storage unit 818 in a well-known manner.
  • the removable storage unit 818 may include a removable storage media that may be read by and written to by the removable storage drive 814 .
  • the removable storage drive 814 is a floppy disk drive
  • the removable storage unit 818 may be a floppy disk.
  • the removable storage unit 818 may be non-transitory computer readable recording media.
  • the secondary memory 810 may include alternative means for allowing computer programs or other instructions to be loaded into the computer system 800 , for example, the removable storage unit 822 and an interface 820 .
  • Examples of such means may include a program cartridge and cartridge interface (e.g., as found in video game systems), a removable memory chip (e.g., EEPROM, PROM, etc.) and associated socket, and other removable storage units 822 and interfaces 820 as will be apparent to persons having skill in the relevant art.
  • the computer system 800 may also include a communications interface 824 .
  • the communications interface 824 may be configured to allow software and data to be transferred between the computer system 800 and external devices.
  • Exemplary communications interfaces 824 may include a modem, a network interface (e.g., an Ethernet card), a communications port, a PCMCIA slot and card, etc.
  • Software and data transferred via the communications interface 824 may be in the form of signals, which may be electronic, electromagnetic, optical, or other signals as will be apparent to persons having skill in the relevant art.
  • the signals may travel via a communications path 826 , which may be configured to carry the signals and may be implemented using wire, cable, fiber optics, a phone line, a cellular phone link, a radio frequency link, etc.
  • Computer program medium and computer usable medium may refer to memories, such as the main memory 808 and secondary memory 810 , which may be memory semiconductors (e.g. DRAMs, etc.). These computer program products may be means for providing software to the computer system 800 .
  • Computer programs e.g., computer control logic
  • Computer programs may be stored in the main memory 808 and/or the secondary memory 810 .
  • Computer programs may also be received via the communications interface 824 .
  • Such computer programs, when executed, may enable computer system 800 to implement the present methods as discussed herein.
  • the computer programs, when executed may enable processor device 804 to implement the methods illustrated by FIGS. 6A , 6 B, 7 A, 7 B, 9 , and 10 , as discussed herein.
  • Such computer programs may represent controllers of the computer system 800 .
  • the software may be stored in a computer program product and loaded into the computer system 800 using the removable storage drive 814 , interface 820 , and hard disk drive 812 , or communications interface 824 .
  • FIG. 9 illustrates a method 900 for initiating a financial transaction using a mobile device (e.g., the mobile device 102 ).
  • a transmitter of the mobile device 102 may transmit a wallet identifier associated with the mobile device 102 .
  • the wallet identifier may be a unique value.
  • the wallet identifier may be at least one of a media access control address, a serial number, an e-mail address, and a phone number.
  • transmitting the wallet identifier may include transmitting the wallet identifier using near field communication.
  • transmitting the wallet identifier may include display (e.g., via the display unit 208 ) a machine readable code encoded with the wallet identifier.
  • the machine readable code may be a bar code.
  • the bar code may be a QR code.
  • a receiver of the mobile device 102 may receive transaction information for a financial transaction to be initiated, wherein the transaction information includes at least a transaction amount (e.g., the transaction amount 404 ).
  • the transaction information may further include an identification of deals that are be valid for the financial transaction to be initiated.
  • step 906 at least one deal and a payment card (e.g., the payment card 414 ) may be stored in a database (e.g., the deal database 104 ), wherein each deal of the at least one deal includes at least a discount amount (e.g., the discount amount 408 ).
  • the discount amount may be a number.
  • the discount amount may be an integer or a percentage.
  • an indication of a deal (e.g., the deal 406 ) of the at least one deal to be applied to the financial transaction to be initiated may be received via an input (e.g., the input unit 210 ) of the mobile device 102 .
  • the input may be a capacitive touch screen display.
  • the indicated deal may be one of the deals identified as valid for the financial transaction to be initiated.
  • a processor e.g., the processing unit 206 of the mobile device 102 may initiate a financial transaction by transmitting, via the transmitting unit 202 , an authorization request using the payment card 414 for the financial transaction, wherein the authorization request includes the payment card 414 and is for a remaining amount (e.g., the remaining amount 412 ), and wherein the remaining amount 402 is based on the transaction amount 404 and the discount amount 408 corresponding to the indicated deal 406 .
  • the authorization request includes the payment card 414 and is for a remaining amount (e.g., the remaining amount 412 )
  • the remaining amount 402 is based on the transaction amount 404 and the discount amount 408 corresponding to the indicated deal 406 .
  • FIG. 10 illustrates a method 1000 for initiating a financial transaction using a merchant point-of-sale (e.g., the merchant 106 ).
  • a merchant point-of-sale e.g., the merchant 106
  • a transaction amount for a financial transaction to be initiated may be identified by a processing device (e.g., the processing unit 302 ).
  • a wallet identifier associated with a mobile device e.g., the mobile device 102
  • the wallet identifier may be received from a receiving device (e.g., the receiving unit 304 ).
  • the wallet identifier may be at least one of a media control access address, a serial number, an e-mail address, and a phone number.
  • receiving the wallet identifier may include receiving the wallet identifier using near field communication.
  • receiving the wallet identifier may include reading, by a reading device, a machine readable code (e.g., the machine readable code 502 ) encoded with the wallet identifier and displayed by the mobile device 102 .
  • the machine readable code may be a bar code.
  • the bar code may be a QR code.
  • receiving the wallet identifier may include reading, by a reading device, a magnetic media encoded with the wallet identifier.
  • the magnetic media may be a payment card.
  • step 1006 at least the wallet identifier and the transaction amount may be transmitted (e.g., via the transmitting unit 306 ) to a server (e.g., the financial transaction processing server 108 ).
  • step 1008 deal information corresponding to a deal to be applied to the financial transaction to be initiated may be received (e.g., by the receiving unit 304 ) from the financial transaction processing server 108 , wherein the deal information includes at least a discount amount.
  • the discount amount may be a number.
  • the discount amount may be an integer or a percentage.
  • a financial transaction may be initiated by the processing unit 302 by transmitting, via the transmitting unit 306 , an authorization request for the financial transaction, wherein the authorization request is for a remaining amount and wherein the remaining amount is based on the transaction amount and the discount amount corresponding to the deal.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Theoretical Computer Science (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Finance (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Game Theory and Decision Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

A method for initiating a financial transaction on a mobile device includes: transmitting, by a transmitter, a wallet identifier associated with the mobile device; receiving, by a receiver, transaction information for a financial transaction to be initiated, wherein the transaction information includes at least a transaction amount; storing, in a database, at least one deal and a payment card, wherein each deal of the at least one deal includes at least a discount amount; receiving, via an input, an indication of a deal of the at least one deal to be applied to the financial transaction to be initiated; and initiating, by a processor, a financial transaction by transmitting an authorization request for the financial transaction, wherein the authorization request includes the payment card and is for a remaining amount, the remaining amount based on the transaction amount and the discount amount corresponding to the indicated deal.

Description

    FIELD
  • The present disclosure relates to the redemption of daily deals using an electronic wallet, specifically the selection of a deal and payment card to be applied to a transaction on a mobile device and then the initiation of the financial transaction by that mobile device or a merchant point-of-sale.
  • BACKGROUND
  • Many consumers have begun to utilize electronic wallets as a more secure and more convenient method for paying for in-person financial transactions with merchants. At the same time, many consumers have also begun to use deals (e.g., coupons, discounts, offers, etc.). However, the deals that consumers wish to use at a merchant often come in a physical form. The deal is presented to the merchant, who then must verify the validity of the deal and apply it to the transaction using their existing point-of-sale technology. This process can be time consuming for the merchant, and is also inefficient for the consumer who must maintain both the physical deal as well as the electronic wallet.
  • Thus, there is a need for a mobile device that uses an electronic wallet to store both deal and payment information that can initiate the financial transaction based on transaction details provided by the merchant without the need for additional verification and the use of physical media.
  • SUMMARY
  • The present disclosure provides a description of a systems and methods for redemption of a deal using an electronic wallet by initiating a financial transaction on a mobile device or a merchant point-of-sale.
  • A method for initiating a financial transaction on a mobile device includes: transmitting, by a transmitter of the mobile device, a wallet identifier associated with the mobile device; receiving, by a receiver of a mobile device, transaction information for a financial transaction to be initiated, wherein the transaction information includes at least a transaction amount; storing, in a database, at least one deal and a payment card, wherein each deal of the at least one deal includes at least a discount amount; receiving, via an input of the mobile device, an indication of a deal of the at least one deal to be applied to the financial transaction to be initiated; and initiating, by a processor of the mobile device, a financial transaction using the payment card by transmitting, via the transmitter, an authorization request for the financial transaction, wherein the authorization request includes the payment card and is for a remaining amount, and wherein the remaining amount is based on the transaction amount and the discount amount corresponding to the indicated deal.
  • A method for initiating a financial transaction includes: identifying, by a processing device, a transaction amount for a financial transaction to be initiated; receiving, from a receiving device, a wallet identifier associated with a mobile device; transmitting, to a server, at least the transaction amount and the wallet identifier; receiving, from the server, deal information corresponding to a deal to be applied to the financial transaction to be initiated, wherein the deal information includes at least a discount amount; initiating, by a processing device, a financial transaction by transmitting, via a transmitting device, an authorization request for the financial transaction, wherein the authorization request is for a remaining amount, and wherein the remaining amount is based on the transaction amount and the discount amount corresponding to the deal.
  • A mobile device for initiating a financial transaction includes a transmitting device, a receiving device, a database, an input device, and a processor. The transmitting device is configured to transmit a wallet identifier associated with the mobile device. The receiving device is configured to receive transaction information for a financial transaction to be initiated, wherein the transaction information includes at least a transaction amount. The database is configured to store at least one deal and a payment card, wherein each deal of the at least one deal includes at least a discount amount. The input device is configured to read an indication of a deal of the at least one deal to be applied to the financial transaction to be initiated. The processor is configured to initiate a financial transaction using the payment card by transmitting, via the transmitter, an authorization request for the financial transaction, wherein the authorization request includes the payment card and is for a remaining amount, and wherein the remaining amount is based on the transaction amount and the discount amount corresponding to the indicated deal.
  • A system for initiating a financial transaction includes a processing device, a receiving device, and a transmitting device. The processing device is configured to identify a transaction amount for a financial transaction to be initiated. The receiving device is configured to receive a wallet identifier associated with a mobile device. The transmitting device is configured to transmit, to a server, at least the transaction amount and the wallet identifier. The receiving device is further configured to receive, from the server, deal information corresponding to a deal to be applied to the financial transaction to be initiated, wherein the deal information includes at least a discount amount. The processing device is further configured to initiate a financial transaction by causing the transmitting device to transmit an authorization request for the financial transaction, and wherein the authorization request is for a remaining amount, and the remaining amount is based on the transaction amount and the discount amount corresponding to the deal.
  • BRIEF DESCRIPTION OF THE DRAWING FIGURES
  • Exemplary embodiments are best understood from the following detailed description when read in conjunction with the accompanying drawings. Included in the drawings are the following figures:
  • FIG. 1 is a block diagram illustrating a system for redeeming a deal and initiating a financial transaction with an electronic wallet in accordance with exemplary embodiments.
  • FIG. 2 is a block diagram illustrating a mobile device in accordance with exemplary embodiments.
  • FIG. 3 is a block diagram illustrating the merchant of FIG. 1 in accordance with exemplary embodiments.
  • FIGS. 4A and 4B are diagrams illustrating a graphical user interface for applying a deal and initiating a financial transaction using an electronic wallet in accordance with exemplary embodiments.
  • FIGS. 5A and 5B are diagrams illustrating graphical user interfaces for transmitting wallet identifiers to a merchant receiving device in accordance with exemplary embodiments.
  • FIGS. 6A and 6B are flow diagrams illustrating a method for initiating a financial transaction using an electronic wallet of a mobile device in accordance with exemplary embodiments.
  • FIGS. 7A and 7B are flow diagrams illustrating a method for initiating a financial transaction using an electronic wallet via a merchant point-of-sale in accordance with exemplary embodiments.
  • FIG. 8 is a block diagram illustrating system architecture of a computer system in accordance with exemplary embodiments.
  • FIGS. 9 and 10 are flow charts illustrating exemplary methods for initiating a financial transaction in accordance with exemplary embodiments.
  • Further areas of applicability of the present disclosure will become apparent from the detailed description provided hereinafter. It should be understood that the detailed description of exemplary embodiments are intended for illustration purposes only and are, therefore, not intended to necessarily limit the scope of the disclosure.
  • DETAILED DESCRIPTION Electronic Wallet
  • An electronic wallet may be a mobile application capable of being stored on and/or executed on a mobile device, such as a smart phone. The electronic wallet may be stored in a memory device located in the mobile device. An electronic wallet may allow a user of the mobile device to enable payment of a financial transaction across multiple channels of commerce by utilizing the electronic wallet application on the mobile device.
  • The electronic wallet may utilize existing payment networks (e.g., operated by MasterCard, VISA, etc.) which are already accepted by merchants, thereby eliminating the need for heavy integration, while providing more security and better economics. Electronic wallets may function with existing authorization techniques (e.g., personal identification numbers, etc.) and not require modification of existing systems. Additional information regarding methods for implementing and using electronic wallets on a mobile device, including the storage and transmission of payment details for financial transactions, can be found in U.S. patent application Ser. No. 13/209,312, filed Aug. 12, 2011, entitled “Mutli-Commerce Channel Wallet for Authenticated Transactions”; U.S. Provisional Patent Application No. 61/605,588, filed Mar. 1, 2012, entitled “Method and Apparatus for Conducting Mobile Payment Transactions”; and U.S. Provisional Patent Application No. 61/619,095, filed Apr. 2, 2012, entitled “System and Method for Processing Mobile Payments for Mobile Devices Without Secure Elements,” each of which are herein incorporated by reference in their entirety.
  • System for Redeeming a Deal Using an Electronic Wallet
  • FIG. 1 illustrates a system 100 for applying a deal using an electronic wallet of a mobile device and initiating a financial transaction using the electronic wallet, or, alternatively, a merchant point of sale. The system 100 may include a mobile device 102. The mobile device 102 may be any type of mobile device suitable for performing the functions as disclosed herein, such as a smart phone, as will be apparent to persons having skill in the relevant art. In an exemplary embodiment, the mobile device 102 may include an electronic wallet application.
  • The mobile device 102 may include a deal database 104. The deal database 104 may be configured to store at least one deal. A deal may be a promotional value that may be applied to a financial transaction with a merchant, such as a discount, a coupon, an offer, etc. A deal may be a discount for a specific product (e.g., $1 off the product) or a stored value for a pre-purchased deal (e.g., user pays $20 to receive $40 worth of goods or services), a discount for a transaction ($10 off any purchase), may be tied to a specific merchant, may require a minimum purchase, etc. Types of deals and offers that may be used in the systems and methods as disclosed herein will be apparent to persons having skill in the relevant art.
  • Each deal in the deal database 104 may include at least a discount amount. In some embodiments, each deal may also include a deal identifier (e.g., for tracking redemption of the deal). The deal database 104 may be included as part of the electronic wallet, may be included as part of the mobile device 102 but not as part of the electronic wallet, or may be external to the mobile device 102 and accessed via a network (e.g., a network 110, discussed in more detail below). For example, the deal database 104 may be included as part of a financial transaction processing agency. The deal database 104 may be a single database or may include multiple databases interfaced together (e.g., physically, or via a network, such as the network 110). Suitable types and configurations of the deal database 104 will be apparent to persons having skill in the relevant art.
  • A user of the mobile device 102 may visit a location (e.g., physical, virtual, etc.) of a merchant 106 to conduct a financial transaction. The merchant 106 may ring up products (e.g., goods or services) for purchase by a user of the mobile device 102. The user may indicate that they wish to apply a deal to the transaction. The user or the mobile device 102 may provide a wallet identifier to the merchant 106, which may be entered by the merchant 106 into the transaction (e.g., using the point-of-sale device). In some embodiments, the merchant 106 may obtain the wallet identifier by transmission of the wallet identifier by the mobile device 102 to a point-of-sale or other device of the merchant 106. For example, the mobile device 102 may transmit the wallet identifier to the merchant 106 via near field communication, the mobile device 102 may display a machine-readable code (e.g., a QR code) encoded with the wallet identifier to be read by the merchant 106, etc. Methods of transmitting the wallet identifier to the merchant 106 will be apparent to persons having skill in the relevant art. In some embodiments, the merchant 106 may receive the wallet identifier by reading magnetic media encoded with the wallet identifier, such as the magnetic strip on a payment card (e.g., for which the user of the mobile device 102 is the cardholder). It will be apparent to persons having skill in the relevant art that reading information (e.g., the wallet identifier) encoded in a payment card may be performed without using a financial transaction processing network and may be done using existing point-of-sale systems.
  • The wallet identifier may be a unique value associated with the mobile device 102, such as a unique number (e.g., a Media Access Control number, phone number, etc.), an e-mail address, a name, or any other value that may be uniquely associated with the mobile device 102. The merchant 106 may transmit purchase details for the potential transaction to a financial transaction processing server 108. The purchase details may include at least the amount of the transaction, the wallet identifier, and a merchant identifier associated with the merchant 106.
  • In one embodiment, the financial transaction processing server 108 may, using the wallet identifier, push at least the amount of the transaction to the mobile device 102. The mobile device 102 may display (e.g., via the electronic wallet application) the transaction to the user and the user may indicate a deal from the deal database 104 to be applied to the transaction. In one embodiment, the electronic wallet may automatically display only those deals that would be valid for the present transaction (e.g., based on the merchant 106, the transaction amount, etc.). In a further embodiment, the information transmitting by the financial transaction processing server 108 may include information indicating only those deals that may be valid for the present transaction. Once a deal has been indicated, the electronic wallet may apply the deal to the transaction (e.g., and reducing the transaction amount based on the discount amount corresponding to the deal) and may prompt the user to select a payment card. The user may select a payment card and the mobile device 102 may initiate a financial transaction for the reduced transaction amount using the selected payment card by submitting an authorization request to the financial transaction processing server 108.
  • In an alternative embodiment, the financial transaction processing server 108 may, using the wallet identifier, transmit deal information corresponding to a deal to be applied to the transaction to the merchant 106. The deal information may include at least a discount amount (e.g., $10, 10%, etc.) for the corresponding deal. The merchant 106 may calculate a remaining amount for the transaction by applying the discount amount to the transaction amount, and may initiate a financial transaction for the remaining amount by submitting an authorization request to the financial transaction processing server 108. It will be apparent to persons having skill in the relevant art that, in this embodiment, the merchant 106 may obtain payment information from the electronic wallet of the mobile device 102 at multiple steps in the process. For example, the merchant 106 may obtain payment details prior to obtaining the wallet identifier, at the same time as obtaining the wallet identifier (e.g., using near field communication), or after applying the deal to the transaction but prior to submitting the authorization request. Methods for transmitting and/or receiving payment details using an electronic wallet will be apparent to persons having skill in the relevant art.
  • The financial transaction processing server 108 may receive the authorization request and may, using methods apparent to those having skill in the relevant art, process the financial transaction for the reduced amount and using the selected payment card. For example, the financial transaction processing server 108 may process the financial transaction using a traditional four party system (e.g., consumer, merchant, acquirer, and issuer). The financial transaction processing server 108 may notify the merchant 106 (e.g., and the mobile device 102) of a response to the authorization request. The merchant 106 may then finalize the transaction (e.g., by providing the goods and/or services to the user of the mobile device 102).
  • Each of the mobile device 102, the merchant 106, and the financial transaction processing server 108 may be configured to communicate via the network 110. The network 110 may be any network suitable for performing the functions as disclosed herein and may include a local area network (LAN), a wide area network (WAN), a wireless network (e.g., WiFi), a mobile communication network, a satellite network, the Internet, fiber optic, coaxial cable, infrared, radio frequency (RF), or any combination thereof. Other suitable network types and configurations will be apparent to persons having skill in the relevant art.
  • Exemplary Mobile Device
  • FIG. 2 illustrates a block diagram of the mobile device 102. The mobile device 102 may include the deal database 104, a transmitting unit 202, a receiving unit 204, a processing unit 206, a display unit 208, and an input unit 210. Each of the components may be connected via a bus 212. Suitable types and configurations of the bus 212 will be apparent to persons having skill in the relevant art.
  • The transmitting unit 202 may be configured to transmit the wallet identifier associated with the mobile device 102 (e.g., to the financial transaction processing server 108 and/or the merchant 106). In one embodiment, the transmitting unit 202 may be configured to transmit the wallet identifier via near field communication. The receiving unit 204 may be configured to receive (e.g., from the financial transaction processing server 108) purchase details for a transaction. The purchase details may include at least the transaction amount, but may also include the merchant identifier, product information, etc.
  • The display unit 208 may be configured to display the received purchase details and at least one deal included in the deal database 104 to the user. The display unit 208 may be any type of display suitable for display information to a user of the mobile device, such as a liquid crystal display (LCD), a light-emitting diode (LED) display, a capacitive touch display, etc. In one embodiment, the processing unit 206 may be configured to identify only deals in the deal database 104 that are valid for application for the purchase. In another embodiment, the purchase details may include deals valid for application for the purchase (e.g., as identified by the financial transaction processing server 108). In one embodiment, the display unit 208 may be configured to display a machine readable code (e.g., a bar code, such as a QR code) encoded with the wallet identifier (e.g., to transmit the wallet identifier to the merchant 106).
  • The input unit 210 may be configured to receive input from a user indicating a deal to be applied to the transaction. The input unit 210 may be any input device suitable for performing the functions as disclosed herein, such as a keyboard, a capacitive touch display, etc. The processing unit 206 may identify the discount amount corresponding to the indicated deal, and may identify a reduced amount based on the transaction amount and the discount amount. The display unit 208 may be configured to display the reduced amount to the user of the mobile device 102. The input unit 210 may be further configured to receive input from a user indicating a payment card to be used for the transaction.
  • Once a payment card has been indicated, the processing unit 206 may be configured to cause the transmitting unit 202 to transmit an authorization request for a financial transaction (e.g., to the financial transaction processing server 108). The authorization request may include the payment card and may be for the reduced amount.
  • Exemplary Merchant Point of Sale
  • FIG. 3 illustrates a block diagram of the merchant 106. The merchant 106 may include a processing unit 302, a receiving unit 304, a transmitting unit 306, a display unit 308, and an input unit 310. Each of the components may be connected via a bus 312. Suitable types and configurations of the bus 312 will be apparent to persons having skill in the relevant art.
  • The processing unit 302 may be configured to identify a transaction amount for a financial transaction to be initiated (e.g., such as through ringing up items at the merchant 106 point-of-sale). The receiving unit 304 may be configured to receive a wallet identifier associated with a mobile device (e.g., the mobile device 102). The receiving unit 304 may receive the wallet identifier using near field communication, by reading a machine readable code (e.g., a QR code) or magnetic media encoded with the wallet identifier, etc. The transmitting unit 306 may be configured to transmit the identified transaction amount and received wallet identifier to a server (e.g., the financial transaction processing server 108).
  • The receiving unit 304 may be further configured to receive (e.g., from the financial transaction processing server 108), deal information corresponding to a deal to be applied to the financial transaction to be initiated. The deal information may include at least a discount amount for the corresponding deal. The processing unit 302 may be configured to apply the discount amount to the transaction amount to obtain a remaining amount for the financial transaction to be initiated. The processing unit 302 may then initiate a financial transaction by causing the transmitting unit 306 to transmit an authorization request for the financial transaction to the financial transaction processing server 108.
  • Graphical User Interfaces
  • FIGS. 4A and 4B illustrate a graphical user interface of the mobile device 102 for the indication of a deal and a payment card for initiating a financial transaction.
  • As illustrated in FIG. 4A, a display 402 of the mobile device 102 may display the electronic wallet application. The application may display a transaction amount 404, which may be received from the financial transaction processing server 108. The application may also display at least one deal 406 that may be applied to the transaction. Each deal displayed may also include a discount amount 408 and a button 410. The user may interact with the button 410 (e.g., via the input unit 210) to indicate the corresponding deal 406 to be applied to the transaction. The processing unit 206 may then apply the deal 406 to the transaction as discussed herein.
  • Once the deal has been applied, the display 402 may display a graphical user interface as illustrated in FIG. 4B. The display 402 may display to the user of the mobile device 102 the transaction amount 404, the discount amount 408 of the indicated deal 406, and a reduced amount 412. The electronic wallet application may also display at least one payment card 414 for use in paying for the transaction. The display of the payment card 414 may include a card identifier 416. The card identifier 416 may include a commercial name for the card, the issuer of the payment card, the payment card number (e.g., which may be partially obscured as illustrated in FIG. 4B), or a customized name or display as selected by the user of the mobile device 102.
  • The payment card 414 may also include a button 418. The user may interact with the button 418 to indicate the payment card 414 for payment. The mobile device 102 may then initiate a financial transaction by transmitting an authorization request to the financial transaction processing server 108. The authorization request may include at least the reduced amount 412 and the payment card 414 to be charged in the transaction. In some embodiments, the display 402 may display a confirmation message to the user once the authorization request has been transmitted and/or a confirmation message may be transmitted to the mobile device 102 (e.g., via electronic mail, short message service, etc.).
  • FIGS. 5A and 5B illustrate graphical user interfaces for the mobile device 102 for the transmitting of the wallet identifier to the merchant 106 (e.g., for initiation of the financial transaction by the merchant 106 point-of-sale).
  • In embodiments where the mobile device 102 may transmit the wallet identifier using machine readable code, the display 402 of the mobile device 102 may display a machine readable code 502. The machine readable code 502 may be encoded with at least the wallet identifier. The machine readable code 502 may be a bar code or any other type of machine readable code suitable for the transmission of the wallet identifier to the merchant 106, such as a QR code as illustrated in FIG. 5A.
  • In embodiments where the mobile device 102 may transmit the wallet identifier using near field communication, the display 402 of the mobile device 102 may display a notification message 504. The notification message 504 may indicate to the user of the mobile device 102 that the mobile device 102 is currently transmitting (e.g., via the transmitting unit 202) the wallet identifier via near field communication. In some embodiments, the display 402 may also display payment card information for the user to indicate a payment card to be transmitted to the merchant 106 in addition to the wallet identifier. For example, the display 402 may display the payment card 414 as illustrated in FIG. 4B. In one embodiment, the user of the mobile device 102 may select the payment card 414 using the wallet application prior to the transmission of information via near field communication, such as indicated in the notification message 504 of FIG. 5B.
  • Method for Redeeming a Deal and Initiating a Financial Transaction Using an Electronic Wallet
  • FIGS. 6A and 6B are a flow diagram illustrating a method for redeeming a deal using an electronic wallet and initiating a financial transaction.
  • In step 602, the merchant 106 may ring up a purchase for a user of the mobile device 102 at the point-of-sale. In step 604, the merchant 106 may enter the wallet identifier associated with the mobile device 102 into the point-of-sale. In one embodiment, the merchant 106 may manually enter the wallet identifier. In another embodiment, the merchant 106 may use a reader device to read a machine-readable code displayed by the mobile device 102 encoded with the wallet identifier. In a further embodiment, the machine-readable code may be a QR code. In one embodiment, the mobile device 102 may transmit the wallet identifier to the merchant 106 point-of-sale using near field communication.
  • In step 606, the merchant 106 may transmit purchase details to the financial transaction processing server 108, who may receive the purchase details in step 608. The purchase details may include at least the transaction amount, the wallet identifier, and a merchant identifier associated with the merchant 106. In step 610, the financial transaction processing server 108 may identify the mobile device 102 based on the wallet identifier and may push (e.g., transmit) the purchase details to the mobile device 102. In step 612, the mobile device 102 may receive (e.g., via the receiving unit 204) the purchase details and may display them (e.g., via the display unit 208) to the user. In one embodiment, the mobile device 102 may also receive from the financial transaction processing server 108 information identifying deals (e.g., stored in the deal database 104) that are valid for applying to the financial transaction to be initiated. In a further embodiment, the mobile device 102 may display only those deals identified as being valid for the financial transaction.
  • In step 614, the mobile device 102 may receive an indication (e.g., via the input unit 210) of a deal (e.g., stored in the deal database 104) to be applied to the purchase and may apply the deal. Application of the deal to the purchase may include identifying (e.g., calculating) a reduced transaction amount based on the transaction amount and a discount amount corresponding to the indicated deal. In step 616, the mobile device 102 may receive an indication of a payment card to be applied to the purchase. Using the indicated payment card, the mobile device 102 may then, in step 618, initiate a financial transaction by transmitting an authorization request. The authorization request may include at least the reduced transaction amount and the payment card.
  • In step 620, the financial transaction processing server 108 may receive the authorization request for the initiated financial transaction. In step 622, the financial transaction processing server 108 may process the financial transaction. Methods for processing a financial transaction will be apparent to persons having skill in the relevant art. In step 624, the financial transaction processing server 108 may transmit an authorization response (e.g., indicating approval or denial of the transaction) to the merchant 106. The merchant 106 may receive the authorization response and, in step 626, may finalize the transaction accordingly. In some embodiments, the financial transaction processing server 108 may also transmit a notification of the processing of the financial transaction to the mobile device 102 (e.g., for display via the display unit 208).
  • Method for Redeeming a Deal and Initiating a Financial Transaction at the Merchant Point-of-Sale
  • FIGS. 7A and 7B are a flow diagram illustrating a method for redeeming a deal of an electronic wallet of a mobile device and initiating a financial transaction via a merchant point-of-sale.
  • In step 702, the merchant 106 may ring up a purchase for a user of the mobile device 102 at the point-of-sale and identify a transaction amount for the purchase. In some embodiments, the merchant 106 may obtain payment details regarding payment for the financial transaction during step 702. In step 704, the mobile device 102 may transmit the wallet identifier to the merchant 106. In one embodiment, the mobile device 102 may transmit the wallet identifier using near field communication. In another embodiment, the wallet identifier may be transmitted by display a machine readable code encoded with the wallet identifier on the mobile device 102. In a further embodiment, the machine readable code may be a bar code. In one embodiment, the bar code may be a QR code. In some embodiments, the mobile device 102 may also transmit payment details in addition to the wallet identifier.
  • In step 706, the merchant 106 may receive the wallet identifier. Then, in step 708, the merchant 106 may transmit purchase details to the financial transaction processing server 108. The purchase details may include at least the identified transaction amount and the received wallet identifier. The financial transaction processing server 108 may receive the purchase details in step 710, and then, in step 712, may identify a deal to be applied to the transaction and push corresponding deal information to the merchant 106. The deal information may include at least a discount amount of the corresponding deal. In one embodiment the discount amount may be an integer (e.g., $10 off) or a percent (e.g., 10% off).
  • In step 714, the merchant 106 may receive the deal information, and then may apply the deal to the purchase in step 716. As part of applying the deal to the purchase, the merchant 106 may calculate, in step 718, a remaining amount for the purchase. In one embodiment, the remaining amount may be calculated by reducing the transaction amount based on the discount amount of the corresponding deal. In step 720, the merchant 106 may initiate a financial transaction by submitting an authorization request to the financial transaction processing server 108 for the remaining transaction amount.
  • In step 722, the financial transaction processing server 108 may receive the authorization request for the initiated financial transaction. In step 724, the financial transaction processing server 108 may process the financial transaction. Methods for processing a financial transaction will be apparent to persons having skill in the relevant art. In step 726, the financial transaction processing server 108 may transmit an authorization response (e.g., indicating approval or denial of the transaction) to the merchant 106. The merchant 106 may receive the authorization response and, in step 728, may finalize the transaction accordingly. In some embodiments, the financial transaction processing server 108 may also transmit a notification of the processing of the financial transaction to the mobile device 102 (e.g., for display via the display unit 208).
  • Computer System Architecture
  • FIG. 8 illustrates a computer system 800 in which embodiments of the present disclosure, or portions thereof, may be implemented as computer-readable code. For example, the deal provider 104, the merchant 106, and the financial transaction processing agency 110 of FIG. 1 may be implemented in the computer system 800 using hardware, software, firmware, non-transitory computer readable media having instructions stored thereon, or a combination thereof and may be implemented in one or more computer systems or other processing systems. Hardware, software, or any combination thereof may embody modules and components used to implement the methods of FIGS. 6A, 6B, 7A, 7B, 9, and 10.
  • If programmable logic is used, such logic may execute on a commercially available processing platform or a special purpose device. A person having ordinary skill in the art may appreciate that embodiments of the disclosed subject matter can be practiced with various computer system configurations, including multi-core multiprocessor systems, minicomputers, mainframe computers, computers linked or clustered with distributed functions, as well as pervasive or miniature computers that may be embedded into virtually any device. For instance, at least one processor device and a memory may be used to implement the above described embodiments.
  • A processor device as discussed herein may be a single processor, a plurality of processors, or combinations thereof. Processor devices may have one or more processor “cores.” The terms “computer program medium,” “non-transitory computer readable medium,” and “computer usable medium” as discussed herein are used to generally refer to tangible media such as a removable storage unit 818, a removable storage unit 822, and a hard disk installed in hard disk drive 812.
  • Various embodiments of the present disclosure are described in terms of this example computer system 800. After reading this description, it will become apparent to a person skilled in the relevant art how to implement the present disclosure using other computer systems and/or computer architectures. Although operations may be described as a sequential process, some of the operations may in fact be performed in parallel, concurrently, and/or in a distributed environment, and with program code stored locally or remotely for access by single or multi-processor machines. In addition, in some embodiments the order of operations may be rearranged without departing from the spirit of the disclosed subject matter.
  • Processor device 804 may be a special purpose or a general purpose processor device. The processor device 804 may be connected to a communication infrastructure 806, such as a bus, message queue, network (e.g., the network 110), multi-core message-passing scheme, etc. The computer system 800 may also include a main memory 508 (e.g., random access memory, read-only memory, etc.), and may also include a secondary memory 810. The secondary memory 810 may include the hard disk drive 812 and a removable storage drive 814, such as a floppy disk drive, a magnetic tape drive, an optical disk drive, a flash memory, etc.
  • The removable storage drive 814 may read from and/or write to the removable storage unit 818 in a well-known manner. The removable storage unit 818 may include a removable storage media that may be read by and written to by the removable storage drive 814. For example, if the removable storage drive 814 is a floppy disk drive, the removable storage unit 818 may be a floppy disk. In one embodiment, the removable storage unit 818 may be non-transitory computer readable recording media.
  • In some embodiments, the secondary memory 810 may include alternative means for allowing computer programs or other instructions to be loaded into the computer system 800, for example, the removable storage unit 822 and an interface 820. Examples of such means may include a program cartridge and cartridge interface (e.g., as found in video game systems), a removable memory chip (e.g., EEPROM, PROM, etc.) and associated socket, and other removable storage units 822 and interfaces 820 as will be apparent to persons having skill in the relevant art.
  • The computer system 800 may also include a communications interface 824. The communications interface 824 may be configured to allow software and data to be transferred between the computer system 800 and external devices. Exemplary communications interfaces 824 may include a modem, a network interface (e.g., an Ethernet card), a communications port, a PCMCIA slot and card, etc. Software and data transferred via the communications interface 824 may be in the form of signals, which may be electronic, electromagnetic, optical, or other signals as will be apparent to persons having skill in the relevant art. The signals may travel via a communications path 826, which may be configured to carry the signals and may be implemented using wire, cable, fiber optics, a phone line, a cellular phone link, a radio frequency link, etc.
  • Computer program medium and computer usable medium may refer to memories, such as the main memory 808 and secondary memory 810, which may be memory semiconductors (e.g. DRAMs, etc.). These computer program products may be means for providing software to the computer system 800. Computer programs (e.g., computer control logic) may be stored in the main memory 808 and/or the secondary memory 810. Computer programs may also be received via the communications interface 824. Such computer programs, when executed, may enable computer system 800 to implement the present methods as discussed herein. In particular, the computer programs, when executed, may enable processor device 804 to implement the methods illustrated by FIGS. 6A, 6B, 7A, 7B, 9, and 10, as discussed herein. Accordingly, such computer programs may represent controllers of the computer system 800. Where the present disclosure is implemented using software, the software may be stored in a computer program product and loaded into the computer system 800 using the removable storage drive 814, interface 820, and hard disk drive 812, or communications interface 824.
  • A First Exemplary Method for Initiating a Financial Transaction
  • FIG. 9 illustrates a method 900 for initiating a financial transaction using a mobile device (e.g., the mobile device 102).
  • In step 902, a transmitter of the mobile device 102 (e.g., the transmitting unit 202) may transmit a wallet identifier associated with the mobile device 102. In one embodiment, the wallet identifier may be a unique value. In a further embodiment, the wallet identifier may be at least one of a media access control address, a serial number, an e-mail address, and a phone number. In one embodiment, transmitting the wallet identifier may include transmitting the wallet identifier using near field communication. In another embodiment, transmitting the wallet identifier may include display (e.g., via the display unit 208) a machine readable code encoded with the wallet identifier. In a further embodiment, the machine readable code may be a bar code. In an even further embodiment, the bar code may be a QR code.
  • In step 904, a receiver of the mobile device 102 (e.g., the receiving unit 204) may receive transaction information for a financial transaction to be initiated, wherein the transaction information includes at least a transaction amount (e.g., the transaction amount 404). In one embodiment, the transaction information may further include an identification of deals that are be valid for the financial transaction to be initiated.
  • In step 906, at least one deal and a payment card (e.g., the payment card 414) may be stored in a database (e.g., the deal database 104), wherein each deal of the at least one deal includes at least a discount amount (e.g., the discount amount 408). In one embodiment the discount amount may be a number. In a further embodiment, the discount amount may be an integer or a percentage. In step 908, an indication of a deal (e.g., the deal 406) of the at least one deal to be applied to the financial transaction to be initiated may be received via an input (e.g., the input unit 210) of the mobile device 102. In one embodiment the input may be a capacitive touch screen display. In one embodiment, the indicated deal may be one of the deals identified as valid for the financial transaction to be initiated.
  • In step 901, a processor (e.g., the processing unit 206) of the mobile device 102 may initiate a financial transaction by transmitting, via the transmitting unit 202, an authorization request using the payment card 414 for the financial transaction, wherein the authorization request includes the payment card 414 and is for a remaining amount (e.g., the remaining amount 412), and wherein the remaining amount 402 is based on the transaction amount 404 and the discount amount 408 corresponding to the indicated deal 406.
  • A Second Exemplary Method for Initiating a Financial Transaction
  • FIG. 10 illustrates a method 1000 for initiating a financial transaction using a merchant point-of-sale (e.g., the merchant 106).
  • In step 1002, a transaction amount for a financial transaction to be initiated may be identified by a processing device (e.g., the processing unit 302). In step 1004, a wallet identifier associated with a mobile device (e.g., the mobile device 102) may be received from a receiving device (e.g., the receiving unit 304). In one embodiment, the wallet identifier may be at least one of a media control access address, a serial number, an e-mail address, and a phone number. In one embodiment, receiving the wallet identifier may include receiving the wallet identifier using near field communication. In another embodiment, receiving the wallet identifier may include reading, by a reading device, a machine readable code (e.g., the machine readable code 502) encoded with the wallet identifier and displayed by the mobile device 102. In a further embodiment, the machine readable code may be a bar code. In an even further embodiment, the bar code may be a QR code. In yet another embodiment, receiving the wallet identifier may include reading, by a reading device, a magnetic media encoded with the wallet identifier. In a further embodiment, the magnetic media may be a payment card.
  • In step 1006, at least the wallet identifier and the transaction amount may be transmitted (e.g., via the transmitting unit 306) to a server (e.g., the financial transaction processing server 108). In step 1008, deal information corresponding to a deal to be applied to the financial transaction to be initiated may be received (e.g., by the receiving unit 304) from the financial transaction processing server 108, wherein the deal information includes at least a discount amount. In one embodiment the discount amount may be a number. In a further embodiment the discount amount may be an integer or a percentage.
  • In step 1010, a financial transaction may be initiated by the processing unit 302 by transmitting, via the transmitting unit 306, an authorization request for the financial transaction, wherein the authorization request is for a remaining amount and wherein the remaining amount is based on the transaction amount and the discount amount corresponding to the deal.
  • Techniques consistent with the present disclosure provide, among other features, systems and methods for on redeeming deals using an electronic wallet and initiating a financial transaction. While various exemplary embodiments of the disclosed system and method have been described above it should be understood that they have been presented for purposes of example only, not limitations. It is not exhaustive and does not limit the disclosure to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practicing of the disclosure, without departing from the breadth or scope.

Claims (38)

What is claimed is:
1. A method for initiating a financial transaction on a mobile device, comprising:
transmitting, by a transmitter of a mobile device, a wallet identifier associated with the mobile device;
receiving, by a receiver of the mobile device, transaction information for a financial transaction to be initiated, wherein the transaction information includes at least a transaction amount;
storing, in a database, at least one deal and a payment card, wherein each deal of the at least one deal includes at least a discount amount;
receiving, via an input of the mobile device, an indication of a deal of the at least one deal to be applied to the financial transaction to be initiated; and
initiating, by a processor of the mobile device, a financial transaction using the stored payment card by transmitting, via the transmitter, an authorization request for the financial transaction,
wherein the authorization request includes the payment card and is for a remaining amount, and
wherein the remaining amount is based on the transaction amount and the discount amount corresponding to the indicated deal.
2. The method of claim 1, wherein transmitting the wallet identifier includes transmitting the wallet identifier using near field communication.
3. The method of claim 1, wherein transmitting the wallet identifier includes displaying, by a display of the mobile device, a machine readable code encoded with the wallet identifier.
4. The method of claim 3, wherein the machine readable code is a bar code.
5. The method of claim 4, wherein the bar code is a QR code.
6. The method of claim 1, wherein the transaction information further includes an identification of deals of the at least one deal that are valid for the financial transaction to be initiated.
7. The method of claim 6, wherein the indicated deal is one of the identified deals valid for the financial transaction to be initiated.
8. The method of claim 1, wherein the discount amount is an integer or a percentage.
9. The method of claim 1, wherein the wallet identifier is at least one of a media control access address, a serial number, an e-mail address, and a phone number.
10. A method for initiating a financial transaction, comprising:
identifying, by a processing device, a transaction amount for a financial transaction to be initiated;
receiving, from a receiving device, a wallet identifier associated with a mobile device;
transmitting, to a server, at least the transaction amount and the wallet identifier;
receiving, from the server, deal information corresponding to a deal to be applied to the financial transaction to be initiated, wherein the deal information includes at least a discount amount;
initiating, by a processing device, a financial transaction by transmitting, via a transmitting device, an authorization request for the financial transaction,
wherein the authorization request is for a remaining amount, and
wherein the remaining amount is based on the transaction amount and the discount amount corresponding to the deal.
11. The method of claim 10, wherein receiving the wallet identifier includes receiving the wallet identifier using near field communication.
12. The method of claim 10, wherein receiving the wallet identifier includes reading, by a reading device, a machine readable code encoded with the wallet identifier and displayed by the mobile device.
13. The method of claim 12, wherein the machine readable code is a bar code.
14. The method of claim 13, wherein the bar code is a QR code.
15. The method of claim 10, wherein the received wallet identifier is transmitted by the mobile device.
16. The method of claim 10, wherein receiving the wallet identifier includes reading, by a reading device, a magnetic media encoded with the wallet identifier.
17. The method of claim 16, wherein the magnetic media is a payment card.
18. The method of claim 10, wherein the discount amount is an integer or a percentage.
19. The method of claim 10, wherein the wallet identifier is at least one of a media control access address, a serial number, an e-mail address, and a phone number.
20. A mobile device for initiating a financial transaction, comprising:
a transmitting device configured to transmit a wallet identifier associated with the mobile device;
a receiving device configured to receive transaction information for a financial transaction to be initiated, wherein the transaction information includes at least a transaction amount;
a database configured to store at least one deal and a payment card, wherein each deal of the at least one deal includes at least a discount amount;
an input device configured to read an indication of a deal of the at least one deal to be applied to the financial transaction to be initiated; and
a processing device configured to initiate a financial transaction using the payment card by causing the transmitting device to transmit an authorization request for the financial transaction,
wherein the authorization request includes the payment card and is for a remaining amount, and
wherein the remaining amount is based on the transaction amount and the discount amount corresponding to the indicated deal.
21. The system of claim 20, wherein the transmitting device is configured to transmit the wallet identifier using near field communication.
22. The system of claim 20, wherein the transmitting device is configured to transmit the wallet identifier by causing a display of the mobile device to display a machine readable code encoded with the wallet identifier.
23. The system of claim 22, wherein the machine readable code is a bar code.
24. The system of claim 23, wherein the bar code is a QR code.
25. The system of claim 20, wherein the transaction information further includes an identification of deals of the at least one deal that are valid for the financial transaction to be initiated.
26. The system of claim 25, wherein the indicated deal is one of the identified deals valid for the financial transaction to be initiated.
27. The system of claim 20, wherein the discount amount is an integer or a percentage.
28. The system of claim 20, wherein the wallet identifier is at least one of a media control access address, a serial number, an e-mail address, and a phone number.
29. A system for initiating a financial transaction, comprising:
a processing device configured to identify a transaction amount for a financial transaction to be initiated;
a receiving device configured to receive a wallet identifier associated with a mobile device; and
a transmitting device configured to transmit, to a server, at least the transaction amount and the wallet identifier, wherein
the receiving device is further configured to receive, from the server, deal information corresponding to a deal to be applied to the financial transaction to be initiated, wherein the deal information includes at least a discount amount, and
the processing device is further configured to initiate a financial transaction by causing the transmitting device to transmit an authorization request for the financial transaction, and wherein
the authorization request is for a remaining amount, and
the remaining amount is based on the transaction amount and the discount amount corresponding to the deal.
30. The system of claim 29, wherein the receiving device is configured to receive the wallet identifier using near field communication.
31. The system of claim 29, wherein the receiving device is configured to read a machine readable code encoded with the wallet identifier and displayed by the mobile device.
32. The system of claim 31, wherein the machine readable code is a bar code.
33. The system of claim 32, wherein the bar code is a QR code.
34. The system of claim 29, wherein the received wallet identifier is transmitted by the mobile device.
35. The system of claim 29, wherein the receiving device is configured to read a magnetic media encoded with the wallet identifier.
36. The system of claim 35, wherein the magnetic media is a payment card.
37. The system of claim 29, wherein the discount amount is an integer or a percentage.
38. The system of claim 29, wherein the wallet identifier is at least one of a media control access address, a serial number, an e-mail address, and a phone number.
US13/551,124 2012-07-17 2012-07-17 Method and system for deal redemption by electronic wallet Abandoned US20140025457A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US13/551,124 US20140025457A1 (en) 2012-07-17 2012-07-17 Method and system for deal redemption by electronic wallet
PCT/US2013/050841 WO2014015010A1 (en) 2012-07-17 2013-07-17 Method and system for deal redemption by electronic wallet

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US13/551,124 US20140025457A1 (en) 2012-07-17 2012-07-17 Method and system for deal redemption by electronic wallet

Publications (1)

Publication Number Publication Date
US20140025457A1 true US20140025457A1 (en) 2014-01-23

Family

ID=49947327

Family Applications (1)

Application Number Title Priority Date Filing Date
US13/551,124 Abandoned US20140025457A1 (en) 2012-07-17 2012-07-17 Method and system for deal redemption by electronic wallet

Country Status (2)

Country Link
US (1) US20140025457A1 (en)
WO (1) WO2014015010A1 (en)

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120006891A1 (en) * 2011-07-18 2012-01-12 Tiger T G Zhou Facilitating mobile device payments using product code scanning
US20130297504A1 (en) * 2012-05-04 2013-11-07 Mastercard International Incorporated Transaction data tokenization
US20140025445A1 (en) * 2012-07-17 2014-01-23 Mastercard International Incorporated Method and system for on demand daily deal settlement
US20140351035A1 (en) * 2013-05-22 2014-11-27 Google Inc. Auto-redeemable basket level offers in a prepaid architecture
US20150019317A1 (en) * 2013-07-13 2015-01-15 Spring Marketplace, Inc. Systems and methods to enable offer and rewards marketing and CRM (network) platform
EP3070660A1 (en) * 2015-03-16 2016-09-21 Samsung Electronics Co., Ltd. Payment additional service information processing method and electronic device for supporting the same
US20170193543A1 (en) * 2016-01-04 2017-07-06 Seth Priebatsch Payment system with item-level promotional campaigns redeemable automatically at point-of-sale devices
US9870556B2 (en) 2013-05-22 2018-01-16 Google Llc Split tender in a prepaid architecture
US9898781B1 (en) * 2007-10-18 2018-02-20 Jpmorgan Chase Bank, N.A. System and method for issuing, circulating and trading financial instruments with smart features
US20180253705A1 (en) * 2017-03-01 2018-09-06 Jpmorgan Chase Bank, N.A. Systems and methods for dynamic inclusion of enhanced data in transactions
CN109074589A (en) * 2016-01-05 2018-12-21 维萨国际服务协会 To the general-purpose accessing of stored value card
EP3329436A4 (en) * 2015-07-27 2019-01-02 Mastercard International Incorporated Electronic payment transactions using machine readable code without requiring online connection
US10366387B2 (en) 2013-10-29 2019-07-30 Visa International Service Association Digital wallet system and method
US10546315B2 (en) 2013-07-13 2020-01-28 Bruce Mitchell Systems and methods to enable offer and rewards marketing, and customer relationship management (CRM) network platform
US10909528B1 (en) * 2013-11-26 2021-02-02 Wells Fargo Bank, N.A. Multi channel purchasing for interoperable mobile wallet
US11551250B2 (en) * 2019-05-01 2023-01-10 Mastercard International Incorporated Payment processing system for applying merchant promotions to a push payment transaction
US11727430B2 (en) 2013-07-13 2023-08-15 Bruce Mitchell Tracking transactions across multiple payment processing networks

Citations (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070162337A1 (en) * 2005-11-18 2007-07-12 Gary Hawkins Method and system for distributing and redeeming targeted offers to customers
US20070282677A1 (en) * 2006-05-31 2007-12-06 Carpenter Brown H Method and System for Providing Householding Information to Multiple Merchants
US20080133350A1 (en) * 2006-10-24 2008-06-05 Brigette White Method and apparatus for reward redemption at the point of interaction
US20090036103A1 (en) * 2007-07-30 2009-02-05 First Data Corporation Mobile communication systems and methods for redeeming and reporting coupons
US20090094125A1 (en) * 2007-10-03 2009-04-09 Patrick Killian System for personalized payments via mobile devices
US20100048226A1 (en) * 2008-08-20 2010-02-25 First Data Corporation Managing mobile marketing offers
US20110145049A1 (en) * 2008-05-18 2011-06-16 Philipp Frank Hermann Udo Hertel Dispensing digital objects to an electronic wallet
US20110246284A1 (en) * 2010-04-01 2011-10-06 Gary Chaikin Systems and Methods for Adding Functionality to Merchant Sales and Facilitating Data Collection.
US20110251892A1 (en) * 2010-04-09 2011-10-13 Kevin Laracey Mobile Phone Payment Processing Methods and Systems
US20120203605A1 (en) * 2011-02-09 2012-08-09 American Express Travel Related Services Company, Inc. Systems and methods for facilitating secure transactions
US20120209749A1 (en) * 2011-02-16 2012-08-16 Ayman Hammad Snap mobile payment apparatuses, methods and systems
US20120265685A1 (en) * 2010-11-17 2012-10-18 Sequent Software Inc. System and Method for Physical-World Based Dynamic Contactless Data Emulation in a Portable Communication Device
US20120290472A1 (en) * 2011-05-10 2012-11-15 Mullen Jeffrey D Systems and devices for mobile payment acceptance
US20120310720A1 (en) * 2011-03-31 2012-12-06 Nokia Corporation Method and apparatus for processing coupons/purchases based on radio frequency memory tag detection
US20130046643A1 (en) * 2011-08-19 2013-02-21 Google Inc. Point of sale processing initiated by a single tap
US20130054336A1 (en) * 2011-04-05 2013-02-28 Roam Data Inc System and method for incorporating one-time tokens, coupons, and reward systems into merchant point of sale checkout systems
US20130073361A1 (en) * 2011-09-20 2013-03-21 Jonathan Silver Methods and systems for offering targeted deals to customers and real-time automatic redemption thereof
US20130144700A1 (en) * 2011-12-02 2013-06-06 First Data Corporation Promotion Processing
US20130238455A1 (en) * 2010-04-09 2013-09-12 Kevin Laracey Methods and systems for selecting accounts and offers in payment transactions
US20140164254A1 (en) * 2012-12-10 2014-06-12 James Dene Dimmick Authenticating Remote Transactions Using a Mobile Device
US20140279479A1 (en) * 2011-10-12 2014-09-18 C-Sam, Inc. Nfc paired bluetooth e-commerce
US20140279472A1 (en) * 2013-03-15 2014-09-18 Mastercard International Incorporated System and method for processing financial transactions using a mobile device for payment

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007280065A (en) * 2006-04-06 2007-10-25 Seiko Epson Corp Electronic money settlement system
US20100125510A1 (en) * 2008-11-17 2010-05-20 Smith Steven M System and method of conducting transactions using a mobile wallet system
KR20110106203A (en) * 2010-03-22 2011-09-28 주식회사 한국사이버결제 Electronic payment method on wire or wireless internet using discount coupon
KR20110084865A (en) * 2011-06-30 2011-07-26 정영선 Mobile credit card payment method using mobile id and contact and contactless communication and apparatus for the method

Patent Citations (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070162337A1 (en) * 2005-11-18 2007-07-12 Gary Hawkins Method and system for distributing and redeeming targeted offers to customers
US20070282677A1 (en) * 2006-05-31 2007-12-06 Carpenter Brown H Method and System for Providing Householding Information to Multiple Merchants
US20080133350A1 (en) * 2006-10-24 2008-06-05 Brigette White Method and apparatus for reward redemption at the point of interaction
US20090036103A1 (en) * 2007-07-30 2009-02-05 First Data Corporation Mobile communication systems and methods for redeeming and reporting coupons
US20090094125A1 (en) * 2007-10-03 2009-04-09 Patrick Killian System for personalized payments via mobile devices
US8762211B2 (en) * 2007-10-03 2014-06-24 Mastercard International Incorporated System for personalized payments via mobile devices
US20110145049A1 (en) * 2008-05-18 2011-06-16 Philipp Frank Hermann Udo Hertel Dispensing digital objects to an electronic wallet
US20100048226A1 (en) * 2008-08-20 2010-02-25 First Data Corporation Managing mobile marketing offers
US20110246284A1 (en) * 2010-04-01 2011-10-06 Gary Chaikin Systems and Methods for Adding Functionality to Merchant Sales and Facilitating Data Collection.
US20110251892A1 (en) * 2010-04-09 2011-10-13 Kevin Laracey Mobile Phone Payment Processing Methods and Systems
US20130238455A1 (en) * 2010-04-09 2013-09-12 Kevin Laracey Methods and systems for selecting accounts and offers in payment transactions
US20120265685A1 (en) * 2010-11-17 2012-10-18 Sequent Software Inc. System and Method for Physical-World Based Dynamic Contactless Data Emulation in a Portable Communication Device
US20120203605A1 (en) * 2011-02-09 2012-08-09 American Express Travel Related Services Company, Inc. Systems and methods for facilitating secure transactions
US20120209749A1 (en) * 2011-02-16 2012-08-16 Ayman Hammad Snap mobile payment apparatuses, methods and systems
US20120310720A1 (en) * 2011-03-31 2012-12-06 Nokia Corporation Method and apparatus for processing coupons/purchases based on radio frequency memory tag detection
US20130054336A1 (en) * 2011-04-05 2013-02-28 Roam Data Inc System and method for incorporating one-time tokens, coupons, and reward systems into merchant point of sale checkout systems
US20120290472A1 (en) * 2011-05-10 2012-11-15 Mullen Jeffrey D Systems and devices for mobile payment acceptance
US20130046643A1 (en) * 2011-08-19 2013-02-21 Google Inc. Point of sale processing initiated by a single tap
US20130073361A1 (en) * 2011-09-20 2013-03-21 Jonathan Silver Methods and systems for offering targeted deals to customers and real-time automatic redemption thereof
US20140279479A1 (en) * 2011-10-12 2014-09-18 C-Sam, Inc. Nfc paired bluetooth e-commerce
US20130144700A1 (en) * 2011-12-02 2013-06-06 First Data Corporation Promotion Processing
US20140164254A1 (en) * 2012-12-10 2014-06-12 James Dene Dimmick Authenticating Remote Transactions Using a Mobile Device
US20140279472A1 (en) * 2013-03-15 2014-09-18 Mastercard International Incorporated System and method for processing financial transactions using a mobile device for payment

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
http://www.creditcards.com/credit-card-news/history-credit-card-magnetic-stripe-1273.php *
https://www.youtube.com/watch?v=NKuUzNnb8aQ *
KR1020110106203A English TRANSlation with drawings *

Cited By (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9898781B1 (en) * 2007-10-18 2018-02-20 Jpmorgan Chase Bank, N.A. System and method for issuing, circulating and trading financial instruments with smart features
US20120006891A1 (en) * 2011-07-18 2012-01-12 Tiger T G Zhou Facilitating mobile device payments using product code scanning
US9367841B2 (en) * 2011-07-18 2016-06-14 Tiger T G Zhou Facilitating mobile device payments using product code scanning
US20130297504A1 (en) * 2012-05-04 2013-11-07 Mastercard International Incorporated Transaction data tokenization
US10275764B2 (en) * 2012-05-04 2019-04-30 Mastercard International Incorporated Transaction data tokenization
US11157896B2 (en) 2012-05-04 2021-10-26 Mastercard International Incorporated Transaction data tokenization
US11720883B2 (en) 2012-05-04 2023-08-08 Mastercard International Incorporated Transaction data tokenization
US20140025445A1 (en) * 2012-07-17 2014-01-23 Mastercard International Incorporated Method and system for on demand daily deal settlement
US20140351035A1 (en) * 2013-05-22 2014-11-27 Google Inc. Auto-redeemable basket level offers in a prepaid architecture
US9870556B2 (en) 2013-05-22 2018-01-16 Google Llc Split tender in a prepaid architecture
US10147112B2 (en) 2013-05-22 2018-12-04 Google Llc Delayed processing window in a prepaid architecture
US10592884B2 (en) 2013-05-22 2020-03-17 Google Llc Split tender in a prepaid architecture
US11727430B2 (en) 2013-07-13 2023-08-15 Bruce Mitchell Tracking transactions across multiple payment processing networks
US10546315B2 (en) 2013-07-13 2020-01-28 Bruce Mitchell Systems and methods to enable offer and rewards marketing, and customer relationship management (CRM) network platform
US20150019317A1 (en) * 2013-07-13 2015-01-15 Spring Marketplace, Inc. Systems and methods to enable offer and rewards marketing and CRM (network) platform
US10366387B2 (en) 2013-10-29 2019-07-30 Visa International Service Association Digital wallet system and method
US11568391B1 (en) 2013-11-26 2023-01-31 Wells Fargo Bank, N.A. Multi channel purchasing of interoperable mobile wallet
US12093927B1 (en) 2013-11-26 2024-09-17 Wells Fargo Bank, N.A. Multi channel purchasing of interoperable mobile wallet
US10909528B1 (en) * 2013-11-26 2021-02-02 Wells Fargo Bank, N.A. Multi channel purchasing for interoperable mobile wallet
US10825009B2 (en) 2015-03-16 2020-11-03 Samsung Electronics Co., Ltd. Payment additional service information processing method and electronic device for supporting the same
EP3070660A1 (en) * 2015-03-16 2016-09-21 Samsung Electronics Co., Ltd. Payment additional service information processing method and electronic device for supporting the same
EP3428864A1 (en) * 2015-03-16 2019-01-16 Samsung Electronics Co., Ltd. Payment additional service information processing method and electronic device for supporting the same
EP3329436A4 (en) * 2015-07-27 2019-01-02 Mastercard International Incorporated Electronic payment transactions using machine readable code without requiring online connection
US20170193543A1 (en) * 2016-01-04 2017-07-06 Seth Priebatsch Payment system with item-level promotional campaigns redeemable automatically at point-of-sale devices
US11488197B2 (en) 2016-01-04 2022-11-01 Scvngr, Inc. Payment system with item-level promotional campaigns redeemable automatically at point-of-sale devices
US10853835B2 (en) * 2016-01-04 2020-12-01 Scvngr, Inc. Payment system with item-level promotional campaigns redeemable automatically at point-of-sale devices
US11830027B2 (en) 2016-01-04 2023-11-28 Scvngr, Inc. Payment system with item-level promotional campaigns redeemable automatically at point-of-sale devices
CN109074589A (en) * 2016-01-05 2018-12-21 维萨国际服务协会 To the general-purpose accessing of stored value card
US11620639B2 (en) * 2017-03-01 2023-04-04 Jpmorgan Chase Bank, N.A. Systems and methods for dynamic inclusion of enhanced data in transactions
US20230196338A1 (en) * 2017-03-01 2023-06-22 Jpmorgan Chase Bank, N.A. Systems and methods for dynamic inclusion of enhanced data in transactions
US20180253705A1 (en) * 2017-03-01 2018-09-06 Jpmorgan Chase Bank, N.A. Systems and methods for dynamic inclusion of enhanced data in transactions
US11893575B2 (en) * 2017-03-01 2024-02-06 Jpmorgan Chase Bank, N.A. Systems and methods for dynamic inclusion of enhanced data in transactions
US20240095717A1 (en) * 2017-03-01 2024-03-21 Jpmorgan Chase Bank, N.A. Systems and methods for dynamic inclusion of enhanced data in transactions
US11551250B2 (en) * 2019-05-01 2023-01-10 Mastercard International Incorporated Payment processing system for applying merchant promotions to a push payment transaction

Also Published As

Publication number Publication date
WO2014015010A1 (en) 2014-01-23

Similar Documents

Publication Publication Date Title
US11941595B2 (en) Systems and methods for point of sale deposits
US20140025457A1 (en) Method and system for deal redemption by electronic wallet
AU2013318440B2 (en) Method and system for processing coupons in a near field transaction
US20180315045A1 (en) Payment architecture using machine-readable graphical code
US10839412B2 (en) Method and system for payment card linked offer generation
US10552822B2 (en) System and method for processing financial transactions using a mobile device for payment
US10552832B2 (en) System and method for processing financial transactions funded via limited use virtual payment numbers
US20140046845A1 (en) Method and system for a payment process to reduce fraud
US20140067674A1 (en) Smartphone barcode transactions
US20150066651A1 (en) Method and System for Secure Mobile Payment Processing and Data Analytics
US20150066757A1 (en) Method and system for instant delivery of virtual gift card on mobile platform
US20140249917A1 (en) Method and system for a hosted merchant and cardholder transaction cache
US20140250007A1 (en) Method and system of cookie driven cardholder authentication summary
US20130325575A1 (en) Method and system for processing variable redemption value electronic coupons
US20140025445A1 (en) Method and system for on demand daily deal settlement
US20150127548A1 (en) Method and system for generating one-to-one merchant offers
US20140244376A1 (en) System and method for facilitating off-peak sales using a payment card network
US20140019222A1 (en) Combining credit card information with preferred purchase information
WO2016040576A1 (en) System and method for processing financial transactions using a mobile device for payment

Legal Events

Date Code Title Description
AS Assignment

Owner name: MASTERCARD INTERNATIONAL INCORPORATED, NEW YORK

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MARTINEZ, JOSE-LUIS CELORIO;GILMAN, ANDREA CHRISTINE;REEL/FRAME:028568/0104

Effective date: 20120716

STCV Information on status: appeal procedure

Free format text: APPEAL READY FOR REVIEW

STCV Information on status: appeal procedure

Free format text: ON APPEAL -- AWAITING DECISION BY THE BOARD OF APPEALS

STCV Information on status: appeal procedure

Free format text: BOARD OF APPEALS DECISION RENDERED

STCB Information on status: application discontinuation

Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION