US20140172533A1 - Loyalty account identification - Google Patents
Loyalty account identification Download PDFInfo
- Publication number
- US20140172533A1 US20140172533A1 US13/715,543 US201213715543A US2014172533A1 US 20140172533 A1 US20140172533 A1 US 20140172533A1 US 201213715543 A US201213715543 A US 201213715543A US 2014172533 A1 US2014172533 A1 US 2014172533A1
- Authority
- US
- United States
- Prior art keywords
- user
- merchant
- loyalty account
- loyalty
- list
- 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
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
- G06Q30/0226—Incentive systems for frequent usage, e.g. frequent flyer miles programs or point systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/325—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
- G06Q30/0226—Incentive systems for frequent usage, e.g. frequent flyer miles programs or point systems
- G06Q30/0229—Multi-merchant loyalty card systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
- G06Q30/0238—Discounts or incentives, e.g. coupons or rebates at point-of-sale [POS]
Definitions
- the present disclosure relates generally to loyalty systems, and more particularly to using an identifier on a user payment instrument to identify a user loyalty account.
- users In conventional merchant-consumer relationships, users must maintain loyalty account identification cards to access a loyalty account.
- the user presents a loyalty card or other loyalty identifier to the merchant at a point of sale terminal.
- the merchant can access the loyalty account of the user and apply the transaction details to the loyalty account.
- the merchant system can record the value of the transaction and apply the appropriate number of reward points to the loyalty account.
- the merchant system can identify a particular product and note that the product has been purchased, as in a “buy 4, get 1 free” promotion.
- the loyalty account can register a visit of the user, such as at a fitness club or a religious organization. Any other loyalty account can utilize a loyalty card or other identifier.
- the different merchants frequented by a user may each require a different loyalty account identification card.
- a user may be required to maintain 10 or 20 different cards to obtain loyalty reward points at each of the many associated merchants.
- a loyalty account user in conventional loyalty programs is unable to use a payment instrument card or user device to allow the merchant to access one or more of the multiple loyalty accounts of the user.
- a payment system employs a server configured to store, using one or more computing devices, a loyalty account list associated with a user, the loyalty account list comprising one or more user loyalty accounts; associate an identifier with the loyalty account list; receive information identifying a user loyalty account associated with a merchant, the information comprising an account number for the user loyalty account and an identity of the merchant; associate the user loyalty account with the loyalty account list; receive a request for information identifying a user loyalty account associated with a merchant, the request comprising the identifier received by the merchant from a user payment instrument and an identity of the merchant; determine the user loyalty account associated with the merchant based at least in part on the identifier received by the merchant from the user payment instrument and the identity of the merchant; and provide the information identifying a user loyalty account associated with a merchant.
- a payment instrument comprising a rigid structure and a machine-readable portion affixed to the rigid structure, the machine-readable portion comprising payment information for a payment account and a loyalty account list identifier having associated therewith in a computing system a plurality of loyalty accounts that are each associated with a respective one of a plurality of merchants.
- FIG. 1 is a block diagram depicting a system for using an identifier on a user payment instrument to identify a user loyalty account, in accordance with certain example embodiments.
- FIG. 2 is a block flow diagram depicting a method to configure a loyalty account list on a loyalty system, in accordance with certain example embodiments.
- FIG. 3 is a block flow diagram depicting a method for using an identifier on a user payment instrument to identify a user loyalty account, in accordance with certain example embodiments.
- FIG. 4 is a block flow diagram depicting a computing machine and a module, in accordance with certain example embodiments.
- a payment instrument contains an identifier of a user loyalty account list on a loyalty system.
- the payment instrument can be a credit card, debit card, proxy card, stored value card, peer-to-peer payment card, or any suitable physical card or payment instrument.
- the payment instrument can be a digital wallet or other payment instrument on a user computing device such as a mobile phone.
- the payment instrument can be any other type of wireless payment instrument, such as an RFID device.
- the payment instrument can be a digital wallet or other payment instrument on a user computing device such as a desktop computer for conducting online transactions.
- the identifier can be an identification number generated by the loyalty system or the user, or any other alpha-numeric code.
- the identifier can alternatively be embodied as a digital wallet identification. That is, the identifier can be a code that is associated with a user digital wallet account. Alternatively, the identifier can be any other number or word associated with the user, such as a driver's license number, or a randomly generated number or word. The user may have the option of selecting a desired identifier and may control information in the identifier that may be provided to a merchant.
- the identifier can be embodied as a bar code that is printed or otherwise affixed to a payment instrument.
- a payment instrument such as a credit card
- a payment instrument can have a bar code, QR code, or other identifier disposed thereon and capable of being scanned or otherwise read by a point of sale (“POS”) terminal or other scanner.
- POS point of sale
- this identifier can be printed directly on the payment instrument or attached to the payment instrument using an adhesive.
- the identifier can be encoded on the magnetic stripe on a payment card.
- a data field on the magnetic stripe can contain the identifier and be read by the POS terminal when the payment card is swiped to provide the payment information from the payment card and the identifier to the POS terminal.
- the identifier can be encoded on the secure element of a user computing device, such as a smartphone.
- the identifier can be transmitted as part of the information transmitted when the user “taps” or otherwise initiates a purchase transaction with the user computing device.
- the identifier can be transmitted as part of the payment information transmitted by the user computing device or as a separate transmission at or near the time of the transaction.
- the identifier can be encoded into an RFID payment device or other payment instrument that can be swiped, tapped, or otherwise read at a POS terminal. Any other suitable manner of transmitting the identifier to the merchant can be employed.
- the RFID payment device can comprise payment information and the identifier that are communicated to the POS terminal when paying for a transaction.
- an RFID label comprising the identifier can be affixed to an RFID payment device or other payment instrument via an adhesive, such as a payment card. In this case, the payment information and the identifier can be communicated to the POS terminal separately, although either substantially simultaneously or sequentially.
- the merchant system After receiving the identifier from the user, the merchant system recognizes the loyalty account list identifier and the loyalty system that contains the loyalty account list of the user. The merchant system queries the loyalty system for the user loyalty account that is associated with the merchant. The merchant system and the loyalty system can communicate via the Internet over the network, via email, via text, or any suitable communication technology. Additionally or alternatively, the identifier or other associated data can include instructions for locating the loyalty system and using the loyalty account list to identify a user loyalty account.
- the loyalty system receives the request from the merchant system and accesses the loyalty account list associated with the user identifier.
- the loyalty system identifies from the user's loyalty account list the loyalty account of the user that is associated with the merchant system.
- the loyalty system provides the identified loyalty account number and any suitable details of the user loyalty account to the merchant system.
- the merchant system can access the loyalty list and select the appropriate loyalty account from the loyalty list.
- the merchant system can use the loyalty account details of the user to access the loyalty account of the user on the merchant system.
- the merchant system can maintain the user loyalty account on a server at the merchant system location, on a remote server, on the POS terminal, or in any other suitable location.
- the merchant system can update the user loyalty account with the details of the current transaction.
- FIG. 1 is a block diagram depicting a system for using an identifier on a user payment instrument to identify a user loyalty account, in accordance with certain example embodiments.
- the system 100 includes network devices 110 , 120 , 130 , and 140 that are configured to communicate with one another via one or more networks 105 .
- Each network 105 includes a wired or wireless telecommunication means by which network devices (including devices 110 , 120 , 130 , and 140 ) can exchange data.
- each network 105 can include a local area network (“LAN”), a wide area network (“WAN”), an intranet, an Internet, a mobile telephone network, or any combination thereof.
- LAN local area network
- WAN wide area network
- intranet an Internet
- Internet a mobile telephone network
- Each network device 110 , 120 , 130 , and 140 includes a device having a communication module capable of transmitting and receiving data over the network 105 .
- each network device 110 , 120 , 130 , and 140 can include a server, desktop computer, laptop computer, tablet computer, a television with one or more processors embedded therein and/or coupled thereto, smart phone, handheld computer, personal digital assistant (“PDA”), or any other wired or wireless, processor-driven device.
- PDA personal digital assistant
- the network devices 110 , 120 , 130 , and 140 are operated by end-users or consumers, payment processing system operators, merchant operators, and loyalty system operators, respectively.
- the user 101 can use the communication application 112 , such as a web browser application or a stand-alone application, to view, download, upload, or otherwise access documents or web pages via a distributed network 105 .
- the network 105 includes a wired or wireless telecommunication system or device by which network devices (including devices 110 , 120 , 130 , and 140 ) can exchange data.
- the network 105 can include a local area network (“LAN”), a wide area network (“WAN”), an intranet, an Internet, storage area network (SAN), personal area network (PAN), a metropolitan area network (MAN), a wireless local area network (WLAN), a virtual private network (VPN), a cellular or other mobile communication network, Bluetooth, NFC, or any combination thereof or any other appropriate architecture or system that facilitates the communication of signals, data, and/or messages.
- LAN local area network
- WAN wide area network
- intranet an Internet
- SAN storage area network
- PAN personal area network
- MAN metropolitan area network
- WLAN wireless local area network
- VPN virtual private network
- cellular or other mobile communication network Bluetooth, NFC, or any combination thereof or any other appropriate architecture or system that facilitates the communication of signals, data, and/or messages.
- the user network device 110 may include a digital wallet application module 111 .
- the digital wallet application module 111 may encompass any application, hardware, software, or process the user device 110 may employ to assist the user 101 in completing a purchase.
- the digital wallet application module 111 can interact with the communication application 112 or can be embodied as a companion application of the communication application 112 . As a companion application, the digital wallet application module 111 executes within the communication application 112 . That is, the digital wallet application module 111 may be an application program embedded in the communication application 112 .
- the user device 110 also includes a data storage unit 113 accessible by the digital wallet application module 111 and the communication application 112 .
- the example data storage unit 113 can include one or more tangible computer-readable storage devices.
- the data storage unit 113 can be stored on the user device 110 or can be logically coupled to the user device 110 .
- the data storage unit 113 can include on-board flash memory and/or one or more removable memory cards or removable flash memory.
- the loyalty system 140 includes a data storage unit 147 accessible by the web server 141 .
- the example data storage unit 147 can include one or more tangible computer-readable storage devices.
- the user 101 can use a web server 141 on the loyalty system 140 to view, register, download, upload, or otherwise access the loyalty system 140 via a website (not illustrated) and a communication network 105 .
- the user 101 associates one or more registered loyalty accounts with a loyalty account list 142 of the user 101 .
- the loyalty system 140 can maintain the account list 142 and provide loyalty account information from the account list 142 to merchant systems 130 and authorized requesters.
- Each loyalty account 132 can be an account associated with a reward program, a frequent shopper program, a sales promotion program, or any suitable loyalty program that provides an incentive to a user 101 to patronize a merchant system 130 .
- the user's 101 registration information and account list 142 is saved in the loyalty system's 140 data storage unit 147 and is accessible the by web server 141 .
- the user 101 can utilize a payment instrument card 102 to conduct a financial transaction.
- the payment instrument card 102 can be traditional credit card or other payment card.
- the traditional payment instrument card 102 can be embodied as a plastic card with a magnetic stripe containing the account information.
- the payment instrument card 102 can be embodied as any other type of card that can be used to initiate and conduct a transaction.
- the payment instrument card 102 can be a card or other device with an RFID chip for conducting transactions, a card with a barcode or other machine-readable code, or any suitable type of physical payment instrument card 102 .
- the merchant system 130 may use a web server 135 to view, download, upload, create offers, sell products online, provide rewards, monitor loyalty accounts, or otherwise access the loyalty system 140 via a website 136 and a communication network 105 .
- the merchant system 130 represents an entity that offers products for the user 101 to purchase or use.
- the merchant system 130 includes a point of sale (“POS”) terminal 134 .
- the POS terminal 134 may be operated by a salesperson that enters the purchase data into the POS terminal 134 to complete the purchase transaction.
- the merchant system 130 may be a physical location or an online merchant.
- the merchant system 130 can maintain the user loyalty account 132 on the merchant server 135 , on the POS terminal 134 , a remote server, or a third party server.
- the loyalty account 132 may be maintained by a merchant system operator, such as a written system or a “punch” system.
- the user 101 may request a purchase from the merchant system 130 .
- the purchase is initiated by a wireless “tap” of the mobile device 110 with the POS terminal 134 .
- the purchase is initiated when the user 101 enters an account identification number at the POS terminal 134 or in the mobile device 110 .
- the purchase is initiated online with the merchant server 135 .
- the purchase may be initiated via the merchant website 136 .
- the purchase is initiated by a magnetic stripe card 102 or other physical card.
- the purchase is initiated by use of a permanent/temporary virtual/physical token, QR code, bar code, or other suitable machine-readable medium captured by a terminal reader or POS terminal 134 .
- the merchant's POS terminal 134 interacts with an acquirer (for example Chase PaymentTech, or other third party payment processing companies), the card network (for example VISA, MasterCard, American Express, Discover or other card processing networks), the payment processing system 120 , and the issuer (for example Citibank, CapitalOne, Bank of America, and other financial institutions to authorize payment).
- an acquirer for example Chase PaymentTech, or other third party payment processing companies
- the card network for example VISA, MasterCard, American Express, Discover or other card processing networks
- the payment processing system 120 for example VISA, MasterCard, American Express, Discover or other card processing networks
- the issuer for example Citibank, CapitalOne, Bank of America, and other financial institutions to authorize payment.
- the payment processing system 120 is used by the payment instrument 105 of the user 101 to conduct a financial transaction.
- the user 101 can use a web server 121 on the payment processing system 120 to view, register, download, upload, or otherwise access the payment processing system 120 via a website (not illustrated) and a communication network 105 ).
- the user 101 can configure one or more registered financial card accounts, including bank account debit cards, credit cards, gift cards, loyalty cards, coupons, offers, prepaid offers, store rewards cards, or other type of financial account that can be used to make a purchase or redeem value-added services with a payment account of the user 101 .
- the payment processing system 120 also may function as the issuer for the associated financial account.
- the user's 101 registration information is saved in the payment processing system's 120 data storage unit and is accessible the by web server 121 .
- the components of the example operating environment 100 are described hereinafter with reference to the example methods illustrated in FIG. 2 .
- FIG. 2 is a block flow diagram depicting a method 200 to configure a loyalty account list 142 on a loyalty system 140 , in accordance with certain example embodiments.
- a merchant system 130 registers with a loyalty system 140 .
- the merchant system 130 can allow users 101 to maintain loyalty account identification on the loyalty system 140 instead of, or in addition to, a physical loyalty card or other loyalty program identification device.
- the loyalty system 140 may be a function of a payment processing system.
- the loyalty system 140 may be a function of the payment processing system, the merchant system 130 , or any other suitable system.
- the loyalty system 140 may be an independent system that is not affiliated with a payment processing system, a payment instrument system, or any other system in the transaction processing stream.
- the merchant system 130 is not registered with the loyalty system 140 .
- the merchant system 130 can be given instructions by the loyalty system identifier to access the loyalty account list 142 on the loyalty system 140 .
- the digital wallet application module 111 on a user device 110 can transmit instructions to a merchant system 120 for accessing the loyalty account list 142 .
- the user 101 establishes a loyalty account list 142 on a loyalty system 140 .
- the user 101 can access the loyalty system 140 on a website on the loyalty system web server 141 and configure an account list 142 .
- the user 101 also may create or update a user loyalty account 132 on a loyalty application (not shown) on the user device 110 or on a digital wallet application module 111 on the user device 110 .
- the user 101 and/or the loyalty system 140 can associate an identifier with the loyalty account list 142 .
- the identifier can be an identification number generated by the loyalty system 140 or the user 101 , or any other alpha-numeric code.
- the identifier can alternatively be embodied as an identification number stored on the digital wallet application module 111 and other digital wallet account applications. That is, the identifier can be a code, username, phone number, or other suitable identifier that is associated with a user digital wallet account.
- the ID can be the identifier that the payment processing system 120 uses to identify the digital wallet account.
- the identifier can be any other number associated with the user 101 , such as a driver's license number, or a randomly generated number or word.
- the user 101 establishes a user loyalty account 132 on the merchant system 130 .
- the user 101 can register for a user loyalty account 132 for the merchant system 130 by completing an application at the location of the merchant system 130 , at an online location of the merchant system 130 , on a loyalty application on a user device 110 , at any other suitable location, or via any suitable method.
- the user 101 can be registered automatically by the merchant system 130 by purchasing a product, requesting information from the merchant system 130 , or by performing any qualifying action.
- the user 101 can be registered automatically by the merchant system 130 without performing any action. Any other suitable method for registering for a user loyalty account 132 can be employed.
- the merchant system 130 can issue a physical loyalty card, assign a loyalty account number, provide a loyalty application, or provide any suitable user loyalty account 132 representation.
- the user loyalty account 132 is associated with the loyalty account list 142 of the user 101 on the loyalty system 140 .
- the user 101 can add the user loyalty account 132 to the loyalty account list 142 and discard any loyalty card or other identifier provided by the merchant system 130 .
- the user loyalty account 132 can be added to the loyalty account list 142 via a website on the loyalty system web server 141 , via a loyalty application (not shown) on the user device 110 or on a digital wallet application module 111 on the user device 110 , or via any other suitable user interface system.
- the user 101 can add accounts, delete accounts, or in any suitable manner modify accounts.
- the user 101 can provide a merchant system 130 name, location, contact information, or any other suitable merchant system 130 data.
- the user 101 can provide the loyalty account name, number, or other identifying information.
- the user 110 can provide any suitable rules or other data required for accumulating, redeeming, maintaining, or otherwise utilizing loyalty points are rewards. Any other suitable information can by added to the loyalty account list 142 .
- the user 101 can add more loyalty accounts to the loyalty account list 142 at the time of configuring the account list 142 or at any time in the future.
- the user 101 may maintain the list with any number of loyalty accounts 132 associated with any number of merchant systems 130 that the loyalty system 140 will allow.
- the number of accounts may be limited by the storage capacity of the server 141 or any other practical limits determined by the loyalty system 140 .
- FIG. 3 is a block flow diagram depicting a method 300 for using an identifier on a user payment instrument to identify a user loyalty account 132 , in accordance with certain example embodiments.
- the loyalty account list identifier is provided to the user 101 and is associated with a payment instrument.
- the identifier can be a bar code, QR code, or other identifier capable of being scanned by a point of sale (“POS”) terminal or other scanner.
- the identifier can be affixed to a payment instrument card 102 such as a credit card or a debit card.
- the identifier can be a sticker affixed to the payment instrument, a decal printed on the payment instrument, or any other physical representation of the identifier affixed to the payment instrument.
- the identifier can additionally or alternatively be encoded on the magnetic stripe on a payment instrument card 102 .
- a data field on the magnetic stripe can contain the identifier and be read by the POS terminal 134 when the payment instrument card 102 is swiped.
- the identifier can be encoded on the secure element of a user device 110 such as a smartphone.
- the identifier can be encoded into an RFID device or other payment instrument that can be swiped or tapped at a POS terminal 134 . Any other suitable manner of transmitting the identifier to the merchant system 130 can be employed.
- a user 101 initiates a purchase at a location of a merchant system 130 .
- the merchant system 130 can be at a physical merchant location or an online merchant location.
- the user 101 can select one or more products for purchase and initiate a transaction with the payment instrument card 102 .
- the initiation can be via a physical payment instrument, contactless transaction with a user device 110 , or an online transaction.
- the identifier is provided to the merchant system 130 .
- the identifier can be transmitted as part of the information transmitted when the user “taps” or otherwise initiates a purchase transaction with the user device 110 .
- the identifier can be transmitted as part of the payment information transmitted by the user device 110 or as a separate transmission at or near the time of the transaction.
- An identifier affixed to a payment instrument can be recognized by a barcode reader, QR code scanner, or any other suitable hardware or software of the merchant system 130 .
- a barcode can be read by the barcode scanner associated with a POS terminal 134 and transmitted to the merchant system server 135 or the POS terminal 134 .
- An identifier encoded on a payment instrument such as a magnetic stripe payment instrument card 102 or RFID device, can be detected by the POS terminal 134 .
- a payment instrument such as a magnetic stripe payment instrument card 102 or RFID device
- the POS terminal 134 can recognize the identifier and instructions. Any other suitable manner of transmitting the identifier to the merchant can be employed.
- the merchant system 130 can use the payment information transmitted by the payment instrument card 102 , the user device 110 , or other device to conduct the payment transaction.
- the merchant system 130 can transmit a payment request to the payment processing system 120 .
- the merchant system 130 and the payment processing system 120 can conduct the transaction via the card network, as a peer-to-peer transaction, or via any suitable manner.
- the transaction is a separate transaction from the transmitting of the identifier for the loyalty account list 142 .
- the transmission of the identifier can be conducted at substantially the same time as the payment transaction or at any later time or earlier time.
- the loyalty system 140 and the payment processing system 120 can be functions of the same system or separate systems. In cases where the loyalty system 140 and the payment processing system 120 are part of the same system, the payment information and the loyalty account list identifier can be transmitted together.
- the merchant system 130 provides the identifier to the loyalty system 140 . If the merchant system 130 has established rules for employing the loyalty system 140 , then the merchant system 130 can provide the identifier to the loyalty system 140 and request the user loyalty account 132 data.
- the merchant system 130 may have previously received instructions from the loyalty system 140 for obtaining user loyalty account 132 information for a user 101 .
- the merchant system 130 may have previously employed the loyalty system 140 , may use the loyalty system 140 for other transaction functions, or may for any reason have exchanged information with the loyalty system 140 .
- the merchant system 130 and the loyalty system 140 can communicate via any communication technology available such as an Internet connection over the network 105 , via email, via text, or via any other suitable technology.
- the identifier can provide instructions for contacting the loyalty system 140 and receiving instructions for accessing the loyalty account list 142 .
- the identifier on a user device 110 that transmits the identifier wirelessly to a POS terminal 134 can further provide instructions for the merchant system 130 to communicate with the loyalty system 140 .
- the instructions can provide a website location, a set of directions, or other information that can communicate the instructions for accessing the loyalty system 140 .
- instructions can be printed with a barcode, transmitted from an RFID device, encoded in a magnetic stripe payment instrument card 102 , or in any suitable manner provided to the merchant system 130 .
- the merchant system 130 additionally can provide an identification of the merchant system 130 .
- the identification can be any data or information that allows the loyalty system 140 to identify the merchant for the purposes of determining the appropriate loyalty account 132 from the loyalty account list 142 .
- the merchant system 130 can provide a name, code, username, password, phone number, or any other identification information that will allow the loyalty system 140 to select the appropriate loyalty account 132 .
- the loyalty system 140 accesses the loyalty account list 142 associated with the identifier and identifies the user loyalty account 132 associated with the merchant system 130 .
- the loyalty system 140 can identify a merchant system 130 requesting the user loyalty account information and determine the appropriate user loyalty account 132 from the account list 142 . The loyalty system 140 then can provide the loyalty account 132 to the merchant system 130 .
- the merchant system 130 can be provided with the account list 142 and provided an opportunity to select the appropriate user loyalty account 132 from the account list 142 . Any other manner of determining the appropriate user loyalty account 132 can be employed by the loyalty system 140 and/or the merchant system 130 .
- the loyalty system 140 transmits the user loyalty account 132 information to the merchant system 130 .
- the loyalty system 140 can provide the account number of the user loyalty account 132 and any other suitable information to the merchant system 130 .
- the information can be transmitted to the merchant system 130 or the merchant system 130 can be allowed to extract the user loyalty account information.
- the merchant system 130 uses the user loyalty account information to access the user loyalty account on the merchant system 130 .
- the merchant system 130 can record new transaction information in the user loyalty account.
- the user loyalty account 132 can be maintained by the merchant system 130 on the merchant server 135 .
- the merchant server 135 can a remote system or the server 135 can be located at the location of the merchant system 130 .
- the user loyalty account 132 can be maintained by the POS terminal 134 .
- the POS terminal 134 can be a function of, or otherwise associated, with the merchant server 135 .
- the user loyalty account 132 additionally or alternatively, can be maintained by a third party or other suitable party.
- the user loyalty account 132 can be maintained in a manner other than on a server.
- the user loyalty account 132 can be maintained by a written system at a merchant system 130 .
- the written system can be managed by an operator of the merchant system 130 .
- the merchant system can update the user loyalty account 132 automatically or manually after accessing the user loyalty account 132 . For example, if a qualifying purchase is made by the user 101 , the merchant system 132 can update the user loyalty account 132 by providing the appropriate number of reward points or other loyalty updates to the user loyalty account 132 on the merchant system 130 . In another example, an operator of the merchant system 130 can input updated information into the user loyalty account 132 on the merchant system 130 .
- FIG. 4 depicts a computing machine 2000 and a module 2050 in accordance with certain example embodiments.
- the computing machine 2000 may correspond to any of the various computers, servers, mobile devices, embedded systems, or computing systems presented herein.
- the module 2050 may comprise one or more hardware or software elements configured to facilitate the computing machine 2000 in performing the various methods and processing functions presented herein.
- the computing machine 2000 may include various internal or attached components such as a processor 2010 , system bus 2020 , system memory 2030 , storage media 2040 , input/output interface 2060 , and a network interface 2070 for communicating with a network 2080 .
- the computing machine 2000 may be implemented as a conventional computer system, an embedded controller, a laptop, a server, a mobile device, a smartphone, a set-top box, a kiosk, a vehicular information system, one more processors associated with a television, a customized machine, any other hardware platform, or any combination or multiplicity thereof.
- the computing machine 2000 may be a distributed system configured to function using multiple computing machines interconnected via a data network or bus system.
- the processor 2010 may be configured to execute code or instructions to perform the operations and functionality described herein, manage request flow and address mappings, and to perform calculations and generate commands.
- the processor 2010 may be configured to monitor and control the operation of the components in the computing machine 2000 .
- the processor 2010 may be a general purpose processor, a processor core, a multiprocessor, a reconfigurable processor, a microcontroller, a digital signal processor (“DSP”), an application specific integrated circuit (“ASIC”), a graphics processing unit (“GPU”), a field programmable gate array (“FPGA”), a programmable logic device (“PLD”), a controller, a state machine, gated logic, discrete hardware components, any other processing unit, or any combination or multiplicity thereof.
- DSP digital signal processor
- ASIC application specific integrated circuit
- GPU graphics processing unit
- FPGA field programmable gate array
- PLD programmable logic device
- the processor 2010 may be a single processing unit, multiple processing units, a single processing core, multiple processing cores, special purpose processing cores, co-processors, or any combination thereof. According to certain embodiments, the processor 2010 along with other components of the computing machine 2000 may be a virtualized computing machine executing within one or more other computing machines.
- the system memory 2030 may include non-volatile memories such as read-only memory (“ROM”), programmable read-only memory (“PROM”), erasable programmable read-only memory (“EPROM”), flash memory, or any other device capable of storing program instructions or data with or without applied power.
- the system memory 2030 may also include volatile memories such as random access memory (“RAM”), static random access memory (“SRAM”), dynamic random access memory (“DRAM”), synchronous dynamic random access memory (“SDRAM”). Other types of RAM also may be used to implement the system memory 2030 .
- RAM random access memory
- SRAM static random access memory
- DRAM dynamic random access memory
- SDRAM synchronous dynamic random access memory
- Other types of RAM also may be used to implement the system memory 2030 .
- the system memory 2030 may be implemented using a single memory module or multiple memory modules.
- system memory 2030 is depicted as being part of the computing machine 2000 , one skilled in the art will recognize that the system memory 2030 may be separate from the computing machine 2000 without departing from the scope of the subject technology. It should also be appreciated that the system memory 2030 may include, or operate in conjunction with, a non-volatile storage device such as the storage media 2040 .
- the storage media 2040 may include a hard disk, a floppy disk, a compact disc read only memory (“CD-ROM”), a digital versatile disc (“DVD”), a Blu-ray disc, a magnetic tape, a flash memory, other non-volatile memory device, a solid sate drive (“SSD”), any magnetic storage device, any optical storage device, any electrical storage device, any semiconductor storage device, any physical-based storage device, any other data storage device, or any combination or multiplicity thereof.
- the storage media 2040 may store one or more operating systems, application programs and program modules such as module 2050 , data, or any other information.
- the storage media 2040 may be part of, or connected to, the computing machine 2000 .
- the storage media 2040 may also be part of one or more other computing machines that are in communication with the computing machine 2000 such as servers, database servers, cloud storage, network attached storage, and so forth.
- the module 2050 may comprise one or more hardware or software elements configured to facilitate the computing machine 2000 with performing the various methods and processing functions presented herein.
- the module 2050 may include one or more sequences of instructions stored as software or firmware in association with the system memory 2030 , the storage media 2040 , or both.
- the storage media 2040 may therefore represent examples of machine or computer readable media on which instructions or code may be stored for execution by the processor 2010 .
- Machine or computer readable media may generally refer to any medium or media used to provide instructions to the processor 2010 .
- Such machine or computer readable media associated with the module 2050 may comprise a computer software product.
- a computer software product comprising the module 2050 may also be associated with one or more processes or methods for delivering the module 2050 to the computing machine 2000 via the network 2080 , any signal-bearing medium, or any other communication or delivery technology.
- the module 2050 may also comprise hardware circuits or information for configuring hardware circuits such as microcode or configuration information for an FPGA or other PLD.
- the input/output (“I/O”) interface 2060 may be configured to couple to one or more external devices, to receive data from the one or more external devices, and to send data to the one or more external devices. Such external devices along with the various internal devices may also be known as peripheral devices.
- the I/O interface 2060 may include both electrical and physical connections for operably coupling the various peripheral devices to the computing machine 2000 or the processor 2010 .
- the I/O interface 2060 may be configured to communicate data, addresses, and control signals between the peripheral devices, the computing machine 2000 , or the processor 2010 .
- the I/O interface 2060 may be configured to implement any standard interface, such as small computer system interface (“SCSI”), serial-attached SCSI (“SAS”), fiber channel, peripheral component interconnect (“PCI”), PCI express (PCIe), serial bus, parallel bus, advanced technology attached (“ATA”), serial ATA (“SATA”), universal serial bus (“USB”), Thunderbolt, FireWire, various video buses, and the like.
- SCSI small computer system interface
- SAS serial-attached SCSI
- PCIe peripheral component interconnect
- PCIe PCI express
- serial bus parallel bus
- ATA advanced technology attached
- SATA serial ATA
- USB universal serial bus
- Thunderbolt FireWire
- the I/O interface 2060 may be configured to implement only one interface or bus technology.
- the I/O interface 2060 may be configured to implement multiple interfaces or bus technologies.
- the I/O interface 2060 may be configured as part of, all of, or to operate in conjunction with, the system bus 2020 .
- the I/O interface 2060 may couple the computing machine 2000 to various input devices including mice, touch-screens, scanners, biometric readers, electronic digitizers, sensors, receivers, touchpads, trackballs, cameras, microphones, keyboards, any other pointing devices, or any combinations thereof.
- the I/O interface 2060 may couple the computing machine 2000 to various output devices including video displays, speakers, printers, projectors, tactile feedback devices, automation control, robotic components, actuators, motors, fans, solenoids, valves, pumps, transmitters, signal emitters, lights, and so forth.
- the computing machine 2000 may operate in a networked environment using logical connections through the network interface 2070 to one or more other systems or computing machines across the network 2080 .
- the network 2080 may include wide area networks (WAN), local area networks (LAN), intranets, the Internet, wireless access networks, wired networks, mobile networks, telephone networks, optical networks, or combinations thereof.
- the network 2080 may be packet switched, circuit switched, of any topology, and may use any communication protocol. Communication links within the network 2080 may involve various digital or an analog communication media such as fiber optic cables, free-space optics, waveguides, electrical conductors, wireless links, antennas, radio-frequency communications, and so forth.
- the processor 2010 may be connected to the other elements of the computing machine 2000 or the various peripherals discussed herein through the system bus 2020 . It should be appreciated that the system bus 2020 may be within the processor 2010 , outside the processor 2010 , or both. According to some embodiments, any of the processor 2010 , the other elements of the computing machine 2000 , or the various peripherals discussed herein may be integrated into a single device such as a system on chip (“SOC”), system on package (“SOP”), or ASIC device.
- SOC system on chip
- SOP system on package
- ASIC application specific integrated circuit
- the users may be provided with a opportunity to control whether programs or features collect user information (e.g., information about a user's social network, social actions or activities, profession, a user's preferences, or a user's current location), or to control whether and/or how to receive content from the content server that may be more relevant to the user.
- user information e.g., information about a user's social network, social actions or activities, profession, a user's preferences, or a user's current location
- certain data may be treated in one or more ways before it is stored or used, so that personally identifiable information is removed.
- a user's identity may be treated so that no personally identifiable information can be determined for the user, or a user's geographic location may be generalized where location information is obtained (such as to a city, ZIP code, or state level), so that a particular location of a user cannot be determined.
- location information such as to a city, ZIP code, or state level
- the user may have control over how information is collected about the user and used by a content server.
- Embodiments may comprise a computer program that embodies the functions described and illustrated herein, wherein the computer program is implemented in a computer system that comprises instructions stored in a machine-readable medium and a processor that executes the instructions.
- the embodiments should not be construed as limited to any one set of computer program instructions.
- a skilled programmer would be able to write such a computer program to implement an embodiment of the disclosed embodiments based on the appended flow charts and associated description in the application text. Therefore, disclosure of a particular set of program code instructions is not considered necessary for an adequate understanding of how to make and use embodiments.
- the example embodiments described herein can be used with computer hardware and software that perform the methods and processing functions described previously.
- the systems, methods, and procedures described herein can be embodied in a programmable computer, computer-executable software, or digital circuitry.
- the software can be stored on computer-readable media.
- computer-readable media can include a floppy disk, RAM, ROM, hard disk, removable media, flash memory, memory stick, optical media, magneto-optical media, CD-ROM, etc.
- Digital circuitry can include integrated circuits, gate arrays, building block logic, field programmable gate arrays (FPGA), etc.
Abstract
Using identifiers on user payment instruments to identify user loyalty accounts comprises a method to store a loyalty account list associated with a user, the loyalty account list comprising one or more user loyalty accounts; associate an identifier with the loyalty account list; receive information identifying a user loyalty account associated with a merchant, the information comprising an account number for the user loyalty account and an identity of the merchant; associate the user loyalty account with the loyalty account list; receive a request for information identifying a user loyalty account associated with a merchant, the request comprising the identifier received by the merchant from a user payment instrument and an identity of the merchant; determine the user loyalty account associated with the merchant; and provide the information identifying a user loyalty account associated with a merchant.
Description
- The present disclosure relates generally to loyalty systems, and more particularly to using an identifier on a user payment instrument to identify a user loyalty account.
- In conventional merchant-consumer relationships, users must maintain loyalty account identification cards to access a loyalty account. The user presents a loyalty card or other loyalty identifier to the merchant at a point of sale terminal. The merchant can access the loyalty account of the user and apply the transaction details to the loyalty account. For example, the merchant system can record the value of the transaction and apply the appropriate number of reward points to the loyalty account. In another example, the merchant system can identify a particular product and note that the product has been purchased, as in a “buy 4, get 1 free” promotion. In another example, the loyalty account can register a visit of the user, such as at a fitness club or a religious organization. Any other loyalty account can utilize a loyalty card or other identifier.
- The different merchants frequented by a user may each require a different loyalty account identification card. Thus, a user may be required to maintain 10 or 20 different cards to obtain loyalty reward points at each of the many associated merchants. A loyalty account user in conventional loyalty programs is unable to use a payment instrument card or user device to allow the merchant to access one or more of the multiple loyalty accounts of the user.
- One aspect of the example embodiments described herein provides a computer-implemented method to use identifiers on user payment instruments to identify user loyalty accounts. A payment system employs a server configured to store, using one or more computing devices, a loyalty account list associated with a user, the loyalty account list comprising one or more user loyalty accounts; associate an identifier with the loyalty account list; receive information identifying a user loyalty account associated with a merchant, the information comprising an account number for the user loyalty account and an identity of the merchant; associate the user loyalty account with the loyalty account list; receive a request for information identifying a user loyalty account associated with a merchant, the request comprising the identifier received by the merchant from a user payment instrument and an identity of the merchant; determine the user loyalty account associated with the merchant based at least in part on the identifier received by the merchant from the user payment instrument and the identity of the merchant; and provide the information identifying a user loyalty account associated with a merchant.
- Another aspect of the example embodiments described herein provides a payment instrument, comprising a rigid structure and a machine-readable portion affixed to the rigid structure, the machine-readable portion comprising payment information for a payment account and a loyalty account list identifier having associated therewith in a computing system a plurality of loyalty accounts that are each associated with a respective one of a plurality of merchants.
- These and other aspects, objects, features and advantages of the example embodiments will become apparent to those having ordinary skill in the art upon consideration of the following detailed description of illustrated example embodiments, which include the best mode of carrying out the invention as presently presented.
-
FIG. 1 is a block diagram depicting a system for using an identifier on a user payment instrument to identify a user loyalty account, in accordance with certain example embodiments. -
FIG. 2 is a block flow diagram depicting a method to configure a loyalty account list on a loyalty system, in accordance with certain example embodiments. -
FIG. 3 is a block flow diagram depicting a method for using an identifier on a user payment instrument to identify a user loyalty account, in accordance with certain example embodiments. -
FIG. 4 is a block flow diagram depicting a computing machine and a module, in accordance with certain example embodiments. - In an example embodiment, a payment instrument contains an identifier of a user loyalty account list on a loyalty system. The payment instrument can be a credit card, debit card, proxy card, stored value card, peer-to-peer payment card, or any suitable physical card or payment instrument. Additionally or alternatively, the payment instrument can be a digital wallet or other payment instrument on a user computing device such as a mobile phone. Additionally or alternatively, the payment instrument can be any other type of wireless payment instrument, such as an RFID device. Additionally or alternatively, the payment instrument can be a digital wallet or other payment instrument on a user computing device such as a desktop computer for conducting online transactions.
- The identifier can be an identification number generated by the loyalty system or the user, or any other alpha-numeric code. The identifier can alternatively be embodied as a digital wallet identification. That is, the identifier can be a code that is associated with a user digital wallet account. Alternatively, the identifier can be any other number or word associated with the user, such as a driver's license number, or a randomly generated number or word. The user may have the option of selecting a desired identifier and may control information in the identifier that may be provided to a merchant.
- The identifier can be embodied as a bar code that is printed or otherwise affixed to a payment instrument. For example, a payment instrument, such as a credit card, can have a bar code, QR code, or other identifier disposed thereon and capable of being scanned or otherwise read by a point of sale (“POS”) terminal or other scanner. In certain embodiments, this identifier can be printed directly on the payment instrument or attached to the payment instrument using an adhesive.
- Additionally or alternatively, the identifier can be encoded on the magnetic stripe on a payment card. For example, a data field on the magnetic stripe can contain the identifier and be read by the POS terminal when the payment card is swiped to provide the payment information from the payment card and the identifier to the POS terminal.
- Additionally or alternatively, the identifier can be encoded on the secure element of a user computing device, such as a smartphone. The identifier can be transmitted as part of the information transmitted when the user “taps” or otherwise initiates a purchase transaction with the user computing device. The identifier can be transmitted as part of the payment information transmitted by the user computing device or as a separate transmission at or near the time of the transaction.
- Additionally or alternatively, the identifier can be encoded into an RFID payment device or other payment instrument that can be swiped, tapped, or otherwise read at a POS terminal. Any other suitable manner of transmitting the identifier to the merchant can be employed. In certain embodiments, the RFID payment device can comprise payment information and the identifier that are communicated to the POS terminal when paying for a transaction. In certain other embodiments, an RFID label comprising the identifier can be affixed to an RFID payment device or other payment instrument via an adhesive, such as a payment card. In this case, the payment information and the identifier can be communicated to the POS terminal separately, although either substantially simultaneously or sequentially.
- After receiving the identifier from the user, the merchant system recognizes the loyalty account list identifier and the loyalty system that contains the loyalty account list of the user. The merchant system queries the loyalty system for the user loyalty account that is associated with the merchant. The merchant system and the loyalty system can communicate via the Internet over the network, via email, via text, or any suitable communication technology. Additionally or alternatively, the identifier or other associated data can include instructions for locating the loyalty system and using the loyalty account list to identify a user loyalty account.
- The loyalty system receives the request from the merchant system and accesses the loyalty account list associated with the user identifier. The loyalty system identifies from the user's loyalty account list the loyalty account of the user that is associated with the merchant system. The loyalty system provides the identified loyalty account number and any suitable details of the user loyalty account to the merchant system. Alternatively, the merchant system can access the loyalty list and select the appropriate loyalty account from the loyalty list.
- The merchant system can use the loyalty account details of the user to access the loyalty account of the user on the merchant system. The merchant system can maintain the user loyalty account on a server at the merchant system location, on a remote server, on the POS terminal, or in any other suitable location. The merchant system can update the user loyalty account with the details of the current transaction.
- Turning now to the drawings, in which like numerals represent like (but not necessarily identical) elements throughout the figures, example embodiments are described in detail.
-
FIG. 1 is a block diagram depicting a system for using an identifier on a user payment instrument to identify a user loyalty account, in accordance with certain example embodiments. As depicted inFIG. 1 , thesystem 100 includesnetwork devices more networks 105. - Each
network 105 includes a wired or wireless telecommunication means by which network devices (includingdevices network 105 can include a local area network (“LAN”), a wide area network (“WAN”), an intranet, an Internet, a mobile telephone network, or any combination thereof. Throughout the discussion of example embodiments, it should be understood that the terms “data” and “information” are used interchangeably herein to refer to text, images, audio, video, or any other form of information that can exist in a computer-based environment. - Each
network device network 105. For example, eachnetwork device FIG. 1 , thenetwork devices - The
user 101 can use thecommunication application 112, such as a web browser application or a stand-alone application, to view, download, upload, or otherwise access documents or web pages via a distributednetwork 105. Thenetwork 105 includes a wired or wireless telecommunication system or device by which network devices (includingdevices network 105 can include a local area network (“LAN”), a wide area network (“WAN”), an intranet, an Internet, storage area network (SAN), personal area network (PAN), a metropolitan area network (MAN), a wireless local area network (WLAN), a virtual private network (VPN), a cellular or other mobile communication network, Bluetooth, NFC, or any combination thereof or any other appropriate architecture or system that facilitates the communication of signals, data, and/or messages. - The
communication application 112 can interact with web servers or other computing devices connected to thenetwork 105, including the point ofsale terminal 134 of themerchant system 130, themerchant server 135 of themerchant system 130, and theweb server 141 of theloyalty system 140. - The user network device 110 may include a digital
wallet application module 111. The digitalwallet application module 111 may encompass any application, hardware, software, or process the user device 110 may employ to assist theuser 101 in completing a purchase. The digitalwallet application module 111 can interact with thecommunication application 112 or can be embodied as a companion application of thecommunication application 112. As a companion application, the digitalwallet application module 111 executes within thecommunication application 112. That is, the digitalwallet application module 111 may be an application program embedded in thecommunication application 112. - The user device 110 also includes a
data storage unit 113 accessible by the digitalwallet application module 111 and thecommunication application 112. The exampledata storage unit 113 can include one or more tangible computer-readable storage devices. Thedata storage unit 113 can be stored on the user device 110 or can be logically coupled to the user device 110. For example, thedata storage unit 113 can include on-board flash memory and/or one or more removable memory cards or removable flash memory. - The
loyalty system 140 includes adata storage unit 147 accessible by theweb server 141. The exampledata storage unit 147 can include one or more tangible computer-readable storage devices. - The
user 101 can use aweb server 141 on theloyalty system 140 to view, register, download, upload, or otherwise access theloyalty system 140 via a website (not illustrated) and acommunication network 105. Theuser 101 associates one or more registered loyalty accounts with aloyalty account list 142 of theuser 101. Theloyalty system 140 can maintain theaccount list 142 and provide loyalty account information from theaccount list 142 tomerchant systems 130 and authorized requesters. Eachloyalty account 132 can be an account associated with a reward program, a frequent shopper program, a sales promotion program, or any suitable loyalty program that provides an incentive to auser 101 to patronize amerchant system 130. The user's 101 registration information andaccount list 142 is saved in the loyalty system's 140data storage unit 147 and is accessible the byweb server 141. - The
user 101 can utilize apayment instrument card 102 to conduct a financial transaction. Thepayment instrument card 102 can be traditional credit card or other payment card. The traditionalpayment instrument card 102 can be embodied as a plastic card with a magnetic stripe containing the account information. Thepayment instrument card 102 can be embodied as any other type of card that can be used to initiate and conduct a transaction. For example, thepayment instrument card 102 can be a card or other device with an RFID chip for conducting transactions, a card with a barcode or other machine-readable code, or any suitable type of physicalpayment instrument card 102. - The
merchant system 130 may use aweb server 135 to view, download, upload, create offers, sell products online, provide rewards, monitor loyalty accounts, or otherwise access theloyalty system 140 via awebsite 136 and acommunication network 105. Themerchant system 130 represents an entity that offers products for theuser 101 to purchase or use. Themerchant system 130 includes a point of sale (“POS”)terminal 134. ThePOS terminal 134 may be operated by a salesperson that enters the purchase data into thePOS terminal 134 to complete the purchase transaction. Themerchant system 130 may be a physical location or an online merchant. - The
merchant system 130 can maintain theuser loyalty account 132 on themerchant server 135, on thePOS terminal 134, a remote server, or a third party server. Alternatively, theloyalty account 132 may be maintained by a merchant system operator, such as a written system or a “punch” system. - The
user 101 may request a purchase from themerchant system 130. In an example embodiment, the purchase is initiated by a wireless “tap” of the mobile device 110 with thePOS terminal 134. In an alternative example embodiment, the purchase is initiated when theuser 101 enters an account identification number at thePOS terminal 134 or in the mobile device 110. In another alternative example embodiment, the purchase is initiated online with themerchant server 135. The purchase may be initiated via themerchant website 136. In yet another alternative example embodiment, the purchase is initiated by amagnetic stripe card 102 or other physical card. In yet another alternative example embodiment, the purchase is initiated by use of a permanent/temporary virtual/physical token, QR code, bar code, or other suitable machine-readable medium captured by a terminal reader orPOS terminal 134. The merchant'sPOS terminal 134 interacts with an acquirer (for example Chase PaymentTech, or other third party payment processing companies), the card network (for example VISA, MasterCard, American Express, Discover or other card processing networks), thepayment processing system 120, and the issuer (for example Citibank, CapitalOne, Bank of America, and other financial institutions to authorize payment). - The
payment processing system 120 is used by thepayment instrument 105 of theuser 101 to conduct a financial transaction. Theuser 101 can use aweb server 121 on thepayment processing system 120 to view, register, download, upload, or otherwise access thepayment processing system 120 via a website (not illustrated) and a communication network 105). Theuser 101 can configure one or more registered financial card accounts, including bank account debit cards, credit cards, gift cards, loyalty cards, coupons, offers, prepaid offers, store rewards cards, or other type of financial account that can be used to make a purchase or redeem value-added services with a payment account of theuser 101. Thepayment processing system 120 also may function as the issuer for the associated financial account. The user's 101 registration information is saved in the payment processing system's 120 data storage unit and is accessible the byweb server 121. - The components of the
example operating environment 100 are described hereinafter with reference to the example methods illustrated inFIG. 2 . -
FIG. 2 is a block flow diagram depicting amethod 200 to configure aloyalty account list 142 on aloyalty system 140, in accordance with certain example embodiments. - With reference to
FIGS. 1 and 2 , inblock 205, amerchant system 130 registers with aloyalty system 140. Themerchant system 130 can allowusers 101 to maintain loyalty account identification on theloyalty system 140 instead of, or in addition to, a physical loyalty card or other loyalty program identification device. Theloyalty system 140 may be a function of a payment processing system. Alternatively, theloyalty system 140 may be a function of the payment processing system, themerchant system 130, or any other suitable system. Alternatively, theloyalty system 140 may be an independent system that is not affiliated with a payment processing system, a payment instrument system, or any other system in the transaction processing stream. - In an alternative embodiment, the
merchant system 130 is not registered with theloyalty system 140. Themerchant system 130 can be given instructions by the loyalty system identifier to access theloyalty account list 142 on theloyalty system 140. For example, the digitalwallet application module 111 on a user device 110 can transmit instructions to amerchant system 120 for accessing theloyalty account list 142. - In
block 210, theuser 101 establishes aloyalty account list 142 on aloyalty system 140. Theuser 101 can access theloyalty system 140 on a website on the loyaltysystem web server 141 and configure anaccount list 142. Theuser 101 also may create or update auser loyalty account 132 on a loyalty application (not shown) on the user device 110 or on a digitalwallet application module 111 on the user device 110. - In
block 215, theuser 101 and/or theloyalty system 140 can associate an identifier with theloyalty account list 142. The identifier can be an identification number generated by theloyalty system 140 or theuser 101, or any other alpha-numeric code. The identifier can alternatively be embodied as an identification number stored on the digitalwallet application module 111 and other digital wallet account applications. That is, the identifier can be a code, username, phone number, or other suitable identifier that is associated with a user digital wallet account. The ID can be the identifier that thepayment processing system 120 uses to identify the digital wallet account. Alternatively, the identifier can be any other number associated with theuser 101, such as a driver's license number, or a randomly generated number or word. - In
block 220, theuser 101 establishes auser loyalty account 132 on themerchant system 130. Theuser 101 can register for auser loyalty account 132 for themerchant system 130 by completing an application at the location of themerchant system 130, at an online location of themerchant system 130, on a loyalty application on a user device 110, at any other suitable location, or via any suitable method. Theuser 101 can be registered automatically by themerchant system 130 by purchasing a product, requesting information from themerchant system 130, or by performing any qualifying action. Theuser 101 can be registered automatically by themerchant system 130 without performing any action. Any other suitable method for registering for auser loyalty account 132 can be employed. - The
merchant system 130 can issue a physical loyalty card, assign a loyalty account number, provide a loyalty application, or provide any suitableuser loyalty account 132 representation. - In
block 225, theuser loyalty account 132 is associated with theloyalty account list 142 of theuser 101 on theloyalty system 140. In the example embodiment, theuser 101 can add theuser loyalty account 132 to theloyalty account list 142 and discard any loyalty card or other identifier provided by themerchant system 130. - The
user loyalty account 132 can be added to theloyalty account list 142 via a website on the loyaltysystem web server 141, via a loyalty application (not shown) on the user device 110 or on a digitalwallet application module 111 on the user device 110, or via any other suitable user interface system. Theuser 101 can add accounts, delete accounts, or in any suitable manner modify accounts. When adding auser loyalty account 132, theuser 101 can provide amerchant system 130 name, location, contact information, or any othersuitable merchant system 130 data. Theuser 101 can provide the loyalty account name, number, or other identifying information. The user 110 can provide any suitable rules or other data required for accumulating, redeeming, maintaining, or otherwise utilizing loyalty points are rewards. Any other suitable information can by added to theloyalty account list 142. - The
user 101 can add more loyalty accounts to theloyalty account list 142 at the time of configuring theaccount list 142 or at any time in the future. Theuser 101 may maintain the list with any number of loyalty accounts 132 associated with any number ofmerchant systems 130 that theloyalty system 140 will allow. The number of accounts may be limited by the storage capacity of theserver 141 or any other practical limits determined by theloyalty system 140. - From
block 225, themethod 200 ends. -
FIG. 3 is a block flow diagram depicting amethod 300 for using an identifier on a user payment instrument to identify auser loyalty account 132, in accordance with certain example embodiments. - In
block 305, the loyalty account list identifier is provided to theuser 101 and is associated with a payment instrument. For example, the identifier can be a bar code, QR code, or other identifier capable of being scanned by a point of sale (“POS”) terminal or other scanner. The identifier can be affixed to apayment instrument card 102 such as a credit card or a debit card. The identifier can be a sticker affixed to the payment instrument, a decal printed on the payment instrument, or any other physical representation of the identifier affixed to the payment instrument. - The identifier can additionally or alternatively be encoded on the magnetic stripe on a
payment instrument card 102. For example, a data field on the magnetic stripe can contain the identifier and be read by thePOS terminal 134 when thepayment instrument card 102 is swiped. Additionally or alternatively, the identifier can be encoded on the secure element of a user device 110 such as a smartphone. The identifier can be encoded into an RFID device or other payment instrument that can be swiped or tapped at aPOS terminal 134. Any other suitable manner of transmitting the identifier to themerchant system 130 can be employed. - In
block 310, auser 101 initiates a purchase at a location of amerchant system 130. Themerchant system 130 can be at a physical merchant location or an online merchant location. Theuser 101 can select one or more products for purchase and initiate a transaction with thepayment instrument card 102. As previously described, the initiation can be via a physical payment instrument, contactless transaction with a user device 110, or an online transaction. - In
block 315, the identifier is provided to themerchant system 130. The identifier can be transmitted as part of the information transmitted when the user “taps” or otherwise initiates a purchase transaction with the user device 110. The identifier can be transmitted as part of the payment information transmitted by the user device 110 or as a separate transmission at or near the time of the transaction. - An identifier affixed to a payment instrument can be recognized by a barcode reader, QR code scanner, or any other suitable hardware or software of the
merchant system 130. For example, a barcode can be read by the barcode scanner associated with aPOS terminal 134 and transmitted to themerchant system server 135 or thePOS terminal 134. - An identifier encoded on a payment instrument, such as a magnetic stripe
payment instrument card 102 or RFID device, can be detected by thePOS terminal 134. For example, if a data field on a magnetic stripepayment instrument card 102 contains the identifier and any needed instructions for accessing theloyalty system 140, thePOS terminal 134 can recognize the identifier and instructions. Any other suitable manner of transmitting the identifier to the merchant can be employed. - The
merchant system 130 can use the payment information transmitted by thepayment instrument card 102, the user device 110, or other device to conduct the payment transaction. For example, themerchant system 130 can transmit a payment request to thepayment processing system 120. Themerchant system 130 and thepayment processing system 120 can conduct the transaction via the card network, as a peer-to-peer transaction, or via any suitable manner. The transaction is a separate transaction from the transmitting of the identifier for theloyalty account list 142. The transmission of the identifier can be conducted at substantially the same time as the payment transaction or at any later time or earlier time. Theloyalty system 140 and thepayment processing system 120 can be functions of the same system or separate systems. In cases where theloyalty system 140 and thepayment processing system 120 are part of the same system, the payment information and the loyalty account list identifier can be transmitted together. - In
block 320, themerchant system 130 provides the identifier to theloyalty system 140. If themerchant system 130 has established rules for employing theloyalty system 140, then themerchant system 130 can provide the identifier to theloyalty system 140 and request theuser loyalty account 132 data. Themerchant system 130 may have previously received instructions from theloyalty system 140 for obtaininguser loyalty account 132 information for auser 101. For example, themerchant system 130 may have previously employed theloyalty system 140, may use theloyalty system 140 for other transaction functions, or may for any reason have exchanged information with theloyalty system 140. - The
merchant system 130 and theloyalty system 140 can communicate via any communication technology available such as an Internet connection over thenetwork 105, via email, via text, or via any other suitable technology. - If the
merchant system 130 does not recognize the identifier and theloyalty system 140 that is associated with the identifier, then the identifier can provide instructions for contacting theloyalty system 140 and receiving instructions for accessing theloyalty account list 142. For example, the identifier on a user device 110 that transmits the identifier wirelessly to aPOS terminal 134 can further provide instructions for themerchant system 130 to communicate with theloyalty system 140. The instructions can provide a website location, a set of directions, or other information that can communicate the instructions for accessing theloyalty system 140. - In another example, instructions can be printed with a barcode, transmitted from an RFID device, encoded in a magnetic stripe
payment instrument card 102, or in any suitable manner provided to themerchant system 130. - The
merchant system 130 additionally can provide an identification of themerchant system 130. The identification can be any data or information that allows theloyalty system 140 to identify the merchant for the purposes of determining theappropriate loyalty account 132 from theloyalty account list 142. For example, themerchant system 130 can provide a name, code, username, password, phone number, or any other identification information that will allow theloyalty system 140 to select theappropriate loyalty account 132. - In
block 325, theloyalty system 140 accesses theloyalty account list 142 associated with the identifier and identifies theuser loyalty account 132 associated with themerchant system 130. In an example embodiment, theloyalty system 140 can identify amerchant system 130 requesting the user loyalty account information and determine the appropriateuser loyalty account 132 from theaccount list 142. Theloyalty system 140 then can provide theloyalty account 132 to themerchant system 130. In another example embodiment, themerchant system 130 can be provided with theaccount list 142 and provided an opportunity to select the appropriateuser loyalty account 132 from theaccount list 142. Any other manner of determining the appropriateuser loyalty account 132 can be employed by theloyalty system 140 and/or themerchant system 130. - In
block 330, theloyalty system 140 transmits theuser loyalty account 132 information to themerchant system 130. After identifying the appropriateuser loyalty account 132, theloyalty system 140 can provide the account number of theuser loyalty account 132 and any other suitable information to themerchant system 130. The information can be transmitted to themerchant system 130 or themerchant system 130 can be allowed to extract the user loyalty account information. - In
block 335, themerchant system 130 uses the user loyalty account information to access the user loyalty account on themerchant system 130. Themerchant system 130 can record new transaction information in the user loyalty account. - The
user loyalty account 132 can be maintained by themerchant system 130 on themerchant server 135. Themerchant server 135 can a remote system or theserver 135 can be located at the location of themerchant system 130. Additionally or alternatively, theuser loyalty account 132 can be maintained by thePOS terminal 134. Additionally or alternatively, thePOS terminal 134 can be a function of, or otherwise associated, with themerchant server 135. Theuser loyalty account 132 additionally or alternatively, can be maintained by a third party or other suitable party. Additionally or alternatively, theuser loyalty account 132 can be maintained in a manner other than on a server. For example, theuser loyalty account 132 can be maintained by a written system at amerchant system 130. The written system can be managed by an operator of themerchant system 130. - The merchant system can update the
user loyalty account 132 automatically or manually after accessing theuser loyalty account 132. For example, if a qualifying purchase is made by theuser 101, themerchant system 132 can update theuser loyalty account 132 by providing the appropriate number of reward points or other loyalty updates to theuser loyalty account 132 on themerchant system 130. In another example, an operator of themerchant system 130 can input updated information into theuser loyalty account 132 on themerchant system 130. - From block 345, the
method 300 ends. -
FIG. 4 depicts acomputing machine 2000 and amodule 2050 in accordance with certain example embodiments. Thecomputing machine 2000 may correspond to any of the various computers, servers, mobile devices, embedded systems, or computing systems presented herein. Themodule 2050 may comprise one or more hardware or software elements configured to facilitate thecomputing machine 2000 in performing the various methods and processing functions presented herein. Thecomputing machine 2000 may include various internal or attached components such as aprocessor 2010, system bus 2020,system memory 2030,storage media 2040, input/output interface 2060, and anetwork interface 2070 for communicating with anetwork 2080. - The
computing machine 2000 may be implemented as a conventional computer system, an embedded controller, a laptop, a server, a mobile device, a smartphone, a set-top box, a kiosk, a vehicular information system, one more processors associated with a television, a customized machine, any other hardware platform, or any combination or multiplicity thereof. Thecomputing machine 2000 may be a distributed system configured to function using multiple computing machines interconnected via a data network or bus system. - The
processor 2010 may be configured to execute code or instructions to perform the operations and functionality described herein, manage request flow and address mappings, and to perform calculations and generate commands. Theprocessor 2010 may be configured to monitor and control the operation of the components in thecomputing machine 2000. Theprocessor 2010 may be a general purpose processor, a processor core, a multiprocessor, a reconfigurable processor, a microcontroller, a digital signal processor (“DSP”), an application specific integrated circuit (“ASIC”), a graphics processing unit (“GPU”), a field programmable gate array (“FPGA”), a programmable logic device (“PLD”), a controller, a state machine, gated logic, discrete hardware components, any other processing unit, or any combination or multiplicity thereof. Theprocessor 2010 may be a single processing unit, multiple processing units, a single processing core, multiple processing cores, special purpose processing cores, co-processors, or any combination thereof. According to certain embodiments, theprocessor 2010 along with other components of thecomputing machine 2000 may be a virtualized computing machine executing within one or more other computing machines. - The
system memory 2030 may include non-volatile memories such as read-only memory (“ROM”), programmable read-only memory (“PROM”), erasable programmable read-only memory (“EPROM”), flash memory, or any other device capable of storing program instructions or data with or without applied power. Thesystem memory 2030 may also include volatile memories such as random access memory (“RAM”), static random access memory (“SRAM”), dynamic random access memory (“DRAM”), synchronous dynamic random access memory (“SDRAM”). Other types of RAM also may be used to implement thesystem memory 2030. Thesystem memory 2030 may be implemented using a single memory module or multiple memory modules. While thesystem memory 2030 is depicted as being part of thecomputing machine 2000, one skilled in the art will recognize that thesystem memory 2030 may be separate from thecomputing machine 2000 without departing from the scope of the subject technology. It should also be appreciated that thesystem memory 2030 may include, or operate in conjunction with, a non-volatile storage device such as thestorage media 2040. - The
storage media 2040 may include a hard disk, a floppy disk, a compact disc read only memory (“CD-ROM”), a digital versatile disc (“DVD”), a Blu-ray disc, a magnetic tape, a flash memory, other non-volatile memory device, a solid sate drive (“SSD”), any magnetic storage device, any optical storage device, any electrical storage device, any semiconductor storage device, any physical-based storage device, any other data storage device, or any combination or multiplicity thereof. Thestorage media 2040 may store one or more operating systems, application programs and program modules such asmodule 2050, data, or any other information. Thestorage media 2040 may be part of, or connected to, thecomputing machine 2000. Thestorage media 2040 may also be part of one or more other computing machines that are in communication with thecomputing machine 2000 such as servers, database servers, cloud storage, network attached storage, and so forth. - The
module 2050 may comprise one or more hardware or software elements configured to facilitate thecomputing machine 2000 with performing the various methods and processing functions presented herein. Themodule 2050 may include one or more sequences of instructions stored as software or firmware in association with thesystem memory 2030, thestorage media 2040, or both. Thestorage media 2040 may therefore represent examples of machine or computer readable media on which instructions or code may be stored for execution by theprocessor 2010. Machine or computer readable media may generally refer to any medium or media used to provide instructions to theprocessor 2010. Such machine or computer readable media associated with themodule 2050 may comprise a computer software product. It should be appreciated that a computer software product comprising themodule 2050 may also be associated with one or more processes or methods for delivering themodule 2050 to thecomputing machine 2000 via thenetwork 2080, any signal-bearing medium, or any other communication or delivery technology. Themodule 2050 may also comprise hardware circuits or information for configuring hardware circuits such as microcode or configuration information for an FPGA or other PLD. - The input/output (“I/O”)
interface 2060 may be configured to couple to one or more external devices, to receive data from the one or more external devices, and to send data to the one or more external devices. Such external devices along with the various internal devices may also be known as peripheral devices. The I/O interface 2060 may include both electrical and physical connections for operably coupling the various peripheral devices to thecomputing machine 2000 or theprocessor 2010. The I/O interface 2060 may be configured to communicate data, addresses, and control signals between the peripheral devices, thecomputing machine 2000, or theprocessor 2010. The I/O interface 2060 may be configured to implement any standard interface, such as small computer system interface (“SCSI”), serial-attached SCSI (“SAS”), fiber channel, peripheral component interconnect (“PCI”), PCI express (PCIe), serial bus, parallel bus, advanced technology attached (“ATA”), serial ATA (“SATA”), universal serial bus (“USB”), Thunderbolt, FireWire, various video buses, and the like. The I/O interface 2060 may be configured to implement only one interface or bus technology. Alternatively, the I/O interface 2060 may be configured to implement multiple interfaces or bus technologies. The I/O interface 2060 may be configured as part of, all of, or to operate in conjunction with, the system bus 2020. The I/O interface 2060 may include one or more buffers for buffering transmissions between one or more external devices, internal devices, thecomputing machine 2000, or theprocessor 2010. - The I/
O interface 2060 may couple thecomputing machine 2000 to various input devices including mice, touch-screens, scanners, biometric readers, electronic digitizers, sensors, receivers, touchpads, trackballs, cameras, microphones, keyboards, any other pointing devices, or any combinations thereof. The I/O interface 2060 may couple thecomputing machine 2000 to various output devices including video displays, speakers, printers, projectors, tactile feedback devices, automation control, robotic components, actuators, motors, fans, solenoids, valves, pumps, transmitters, signal emitters, lights, and so forth. - The
computing machine 2000 may operate in a networked environment using logical connections through thenetwork interface 2070 to one or more other systems or computing machines across thenetwork 2080. Thenetwork 2080 may include wide area networks (WAN), local area networks (LAN), intranets, the Internet, wireless access networks, wired networks, mobile networks, telephone networks, optical networks, or combinations thereof. Thenetwork 2080 may be packet switched, circuit switched, of any topology, and may use any communication protocol. Communication links within thenetwork 2080 may involve various digital or an analog communication media such as fiber optic cables, free-space optics, waveguides, electrical conductors, wireless links, antennas, radio-frequency communications, and so forth. - The
processor 2010 may be connected to the other elements of thecomputing machine 2000 or the various peripherals discussed herein through the system bus 2020. It should be appreciated that the system bus 2020 may be within theprocessor 2010, outside theprocessor 2010, or both. According to some embodiments, any of theprocessor 2010, the other elements of thecomputing machine 2000, or the various peripherals discussed herein may be integrated into a single device such as a system on chip (“SOC”), system on package (“SOP”), or ASIC device. - In situations in which the systems discussed here collect personal information about users, or may make use of personal information, the users may be provided with a opportunity to control whether programs or features collect user information (e.g., information about a user's social network, social actions or activities, profession, a user's preferences, or a user's current location), or to control whether and/or how to receive content from the content server that may be more relevant to the user. In addition, certain data may be treated in one or more ways before it is stored or used, so that personally identifiable information is removed. For example, a user's identity may be treated so that no personally identifiable information can be determined for the user, or a user's geographic location may be generalized where location information is obtained (such as to a city, ZIP code, or state level), so that a particular location of a user cannot be determined. Thus, the user may have control over how information is collected about the user and used by a content server.
- Embodiments may comprise a computer program that embodies the functions described and illustrated herein, wherein the computer program is implemented in a computer system that comprises instructions stored in a machine-readable medium and a processor that executes the instructions. However, it should be apparent that there could be many different ways of implementing embodiments in computer programming, and the embodiments should not be construed as limited to any one set of computer program instructions. Further, a skilled programmer would be able to write such a computer program to implement an embodiment of the disclosed embodiments based on the appended flow charts and associated description in the application text. Therefore, disclosure of a particular set of program code instructions is not considered necessary for an adequate understanding of how to make and use embodiments. Further, those skilled in the art will appreciate that one or more aspects of embodiments described herein may be performed by hardware, software, or a combination thereof, as may be embodied in one or more computing systems. Moreover, any reference to an act being performed by a computer should not be construed as being performed by a single computer as more than one computer may perform the act.
- The example embodiments described herein can be used with computer hardware and software that perform the methods and processing functions described previously. The systems, methods, and procedures described herein can be embodied in a programmable computer, computer-executable software, or digital circuitry. The software can be stored on computer-readable media. For example, computer-readable media can include a floppy disk, RAM, ROM, hard disk, removable media, flash memory, memory stick, optical media, magneto-optical media, CD-ROM, etc. Digital circuitry can include integrated circuits, gate arrays, building block logic, field programmable gate arrays (FPGA), etc.
- The example systems, methods, and acts described in the embodiments presented previously are illustrative, and, in alternative embodiments, certain acts can be performed in a different order, in parallel with one another, omitted entirely, and/or combined between different example embodiments, and/or certain additional acts can be performed, without departing from the scope and spirit of various embodiments. Accordingly, such alternative embodiments are included in the inventions described herein.
- Although specific embodiments have been described above in detail, the description is merely for purposes of illustration. It should be appreciated, therefore, that many aspects described above are not intended as required or essential elements unless explicitly stated otherwise. Modifications of, and equivalent components or acts corresponding to, the disclosed aspects of the example embodiments, in addition to those described above, can be made by a person of ordinary skill in the art, having the benefit of the present disclosure, without departing from the spirit and scope of embodiments defined in the following claims, the scope of which is to be accorded the broadest interpretation so as to encompass such modifications and equivalent structures.
Claims (28)
1. A computer-implemented method to use identifiers on user payment instruments to identify user loyalty accounts, comprising:
storing, using one or more computing devices, a loyalty account list associated with a user, the loyalty account list comprising one or more user loyalty accounts;
associating, using the one or more computing devices, a list identifier with the loyalty account list;
encoding the list identifier on a data field of a single magnetic stripe of a magnetic stripe card associated with a payment account of the user, the magnetic stripe comprising the list identifier and separate payment account information for conducting a payment transaction using the payment account, and the list identifier being encoded in a discretionary data field of the magnetic stripe;
receiving, using the one or more computing devices and from a merchant computing device associated with a merchant, information identifying a user loyalty account number for a user loyalty account associated with a merchant, the list identifier for the loyalty account list, and an identity of the merchant, the list identifier being obtained by the merchant from the magnetic stripe card utilized by the user to conduct payment transactions with the merchant;
associating, using the one or more computing devices, the user loyalty account number for the user loyalty account associated with the merchant with the loyalty account list based at least in part on the list identifier received with the user loyalty account number;
receiving, using the one or more computing devices and from the merchant computing device, a request for information identifying the user loyalty account associated with the merchant, the request comprising the identity of the merchant and the list identifier for the loyalty account list, the list identifier being obtained by the merchant from the magnetic stripe card utilized by the user to conduct a payment transaction with the merchant;
determining, using the one or more computing devices, the user loyalty account associated with the merchant in the loyalty account list based at least in part on the identity of the merchant and the list identifier obtained by the merchant from the magnetic stripe card utilized by the user to conduct the payment transaction with the merchant; and
providing, using the one or more computing devices, the requested information identifying the user loyalty account associated with the merchant, the provided information comprising the loyalty account number for the user loyalty account associated with the merchant in the loyalty account list.
2. The computer-implemented method of claim 1 , wherein the list identifier comprises an identification of a digital wallet associated with the user.
3. The computer-implemented method of claim 1 , wherein the request is received at the time of a transaction.
4. (canceled)
5. (canceled)
6. The computer-implemented method of claim 1 , wherein the record identifier is provided to the merchant via a wireless connection with a user computing device.
7. (canceled)
8. The computer-implemented method of claim 1 , wherein the merchant further receives instructions from the user payment instrument for accessing the loyalty account list on the loyalty system.
9. A payment instrument, comprising:
a rigid structure; and
a machine-readable portion affixed to the rigid structure, the machine-readable portion comprising payment information for a payment account and a loyalty account list identifier having associated therewith in a computing system a plurality of loyalty accounts that are each associated with a respective one of a plurality of merchants.
10. The computer-implemented method of claim 9 , wherein machine-readable portion comprises a barcode, a QR code, and an RFID tag.
11. The computer-implemented method of claim 9 , wherein the machine-readable portion is a magnetic stripe, and wherein the payment information and the loyalty account list identifier are encoded in a data field of the magnetic stripe.
12. The payment instrument card of claim 9 , the machine-readable portion further comprising instructions regarding a location of the computing system managing the loyalty account list.
13. A system to transmit category codes to use identifiers on user payment instruments to identify user loyalty accounts, the system comprising:
a storage resource;
a network module; and
a processor communicatively coupled to the storage resource and the network module, wherein the processor executes application code instructions that are stored in the storage resource and that cause the system to:
store a loyalty account record associated with a user, the loyalty account list comprising one or more user loyalty accounts;
associate an identifier with the loyalty account record;
encoding the list identifier on a data field of a magnetic stripe of a magnetic stripe card associated with a payment account of the user, the magnetic stripe comprising the record identifier and separate payment account information for conducting a payment transaction using the payment account;
receive information identifying a user loyalty account number for a user loyalty account associated with a merchant, the record identifier for the loyalty account record, and an identity of the merchant;
associate the user loyalty account with the loyalty account record;
receive a request for information identifying the user loyalty account associated with the merchant, the request comprising the record identifier for the loyalty account record obtained by the merchant and an identity of the merchant, the record identifier for the user loyalty record being obtained by the merchant from the magnetic stripe card utilized by the user to conduct the transaction with the merchant;
determine the user loyalty account associated with the merchant in the loyalty account record based at least in part on the identity of the merchant and the record identifier obtained by the merchant from the magnetic stripe card utilized by the user to conduct the transaction with the merchant; and
provide the requested information identifying the user loyalty account associated with a merchant, the provided information comprising the loyalty account number for the user loyalty account associated with the merchant in the loyalty account record.
14. The system of claim 13 , wherein the record identifier comprises an identification of a digital wallet associated with the user.
15. The system of claim 13 , wherein the request is received at the time of a transaction.
16. (canceled)
17. (canceled)
18. The system of claim 13 , wherein the record identifier is provided to the merchant via a wireless connection with a user computing device.
19. (canceled)
20. The system of claim 13 , wherein the merchant further receives instructions from the user payment instrument for accessing the loyalty account record on the loyalty system.
21. A computer program product, comprising:
a non-transitory computer-readable storage device having computer-executable program instructions embodied thereon that when executed by a computer cause the computer to use identifiers on user payment instruments to identify user loyalty accounts, the computer-executable program instructions comprising:
computer-executable program instructions to store a loyalty account list associated with a user, the loyalty account list comprising one or more user loyalty accounts;
computer-executable program instructions to associate a list identifier with the loyalty account list;
computer-executable program instructions to encode the list identifier on a data field of a single magnetic stripe of a magnetic stripe card associated with a payment account of the user, the magnetic stripe comprising the list identifier and separate payment account information for conducting a payment transaction using the payment account;
computer-executable program instructions to receive information identifying a user loyalty account number for a user loyalty account associated with a merchant, the list identifier for the loyalty account list and an identity of the merchant;
computer-executable program instructions to associate the user loyalty account number for the user loyalty account associated with the merchant with the loyalty account list based at least in part on the list identifier received with the user loyalty account number;
computer-executable program instructions to receive a request for information identifying the user loyalty account associated with the merchant, the request comprising identity of the merchant and the list identifier for the loyalty account list, the list identifier being obtained by the merchant from the magnetic stripe card utilized by the user to conduct a payment transaction with the merchant; and
computer-executable program instructions to provide the loyalty account list to the merchant to allow the merchant to identify the user loyalty account associated with the merchant from the loyalty account list.
22. The computer program product of claim 21 , wherein the list identifier comprises an identification of a digital wallet associated with the user.
23. The computer program product of claim 21 , wherein the request is received at the time of a transaction.
24. (canceled)
25. The computer-implemented method of claim 1 , further comprising providing, using the one or more computing devices, the loyalty account list to the merchant to allow the merchant to identify the user loyalty account associated with the merchant.
26. The system of claim 13 , further comprising instructions to provide the loyalty account record to the merchant to allow the merchant to identify the user loyalty account associated with the merchant.
27. The computer program product of claim 21 , further comprising computer-executable program instructions to encode the list identifier on a data field of a magnetic stripe of a magnetic stripe card associated with a payment account of the user, the magnetic stripe comprising the list identifier and separate payment account information for conducting a payment transaction using the payment account.
28. The computer program product of claim 27 , the list identifier being obtained by the merchant from the magnetic stripe card utilized by the user to conduct payment transactions with the merchant.
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/715,543 US20140172533A1 (en) | 2012-12-14 | 2012-12-14 | Loyalty account identification |
PCT/US2013/075512 WO2014093993A1 (en) | 2012-12-14 | 2013-12-16 | Loyalty account identification |
US15/667,215 US20170330216A1 (en) | 2012-12-14 | 2017-08-02 | Loyalty account identification |
US16/995,578 US11861648B2 (en) | 2012-12-14 | 2020-08-17 | Loyalty account identification |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/715,543 US20140172533A1 (en) | 2012-12-14 | 2012-12-14 | Loyalty account identification |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/667,215 Continuation US20170330216A1 (en) | 2012-12-14 | 2017-08-02 | Loyalty account identification |
Publications (1)
Publication Number | Publication Date |
---|---|
US20140172533A1 true US20140172533A1 (en) | 2014-06-19 |
Family
ID=50932009
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/715,543 Abandoned US20140172533A1 (en) | 2012-12-14 | 2012-12-14 | Loyalty account identification |
US15/667,215 Abandoned US20170330216A1 (en) | 2012-12-14 | 2017-08-02 | Loyalty account identification |
US16/995,578 Active 2033-09-20 US11861648B2 (en) | 2012-12-14 | 2020-08-17 | Loyalty account identification |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/667,215 Abandoned US20170330216A1 (en) | 2012-12-14 | 2017-08-02 | Loyalty account identification |
US16/995,578 Active 2033-09-20 US11861648B2 (en) | 2012-12-14 | 2020-08-17 | Loyalty account identification |
Country Status (2)
Country | Link |
---|---|
US (3) | US20140172533A1 (en) |
WO (1) | WO2014093993A1 (en) |
Cited By (33)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9064252B2 (en) * | 2005-10-11 | 2015-06-23 | National Payment Card Association | Payment system and methods |
US20160358199A1 (en) * | 2015-06-05 | 2016-12-08 | Apple Inc. | User interface for loyalty accounts and private label accounts |
US20160358144A1 (en) * | 2015-06-08 | 2016-12-08 | Google Inc. | Point Of Sale Terminal Geolocations |
US10024682B2 (en) | 2015-02-13 | 2018-07-17 | Apple Inc. | Navigation user interface |
US10043185B2 (en) | 2014-05-29 | 2018-08-07 | Apple Inc. | User interface for payments |
US10066959B2 (en) | 2014-09-02 | 2018-09-04 | Apple Inc. | User interactions for a mapping application |
WO2018165763A1 (en) * | 2017-03-17 | 2018-09-20 | Royal Bank Of Canada | Systems and methods for hybrid blockchain platform |
US20190034916A1 (en) * | 2017-07-25 | 2019-01-31 | Mastercard International Incorporated | Electronic system and method for managing loyalty account identifiers |
US10250735B2 (en) | 2013-10-30 | 2019-04-02 | Apple Inc. | Displaying relevant user interface objects |
US10255595B2 (en) | 2015-02-01 | 2019-04-09 | Apple Inc. | User interface for payments |
WO2019077346A1 (en) * | 2017-10-17 | 2019-04-25 | Payment Loyalty Limited | Improved systems and methods for delivering loyalty incentives |
US10332079B2 (en) | 2015-06-05 | 2019-06-25 | Apple Inc. | User interface for loyalty accounts and private label accounts for a wearable device |
US10395128B2 (en) | 2017-09-09 | 2019-08-27 | Apple Inc. | Implementation of biometric authentication |
US10417656B2 (en) * | 2016-12-27 | 2019-09-17 | Paypal, Inc. | Managing user loyalty groups at point-of-sale accesses |
US10521579B2 (en) | 2017-09-09 | 2019-12-31 | Apple Inc. | Implementation of biometric authentication |
US10621581B2 (en) | 2016-06-11 | 2020-04-14 | Apple Inc. | User interface for transactions |
US10659405B1 (en) | 2019-05-06 | 2020-05-19 | Apple Inc. | Avatar integration with multiple applications |
US10671987B2 (en) * | 2007-06-22 | 2020-06-02 | Ncr Corporation | System and method for interacting with a self-service terminal |
CN111465956A (en) * | 2017-04-24 | 2020-07-28 | 马克西姆.维塔利耶维奇.别克涅夫 | Method for executing payment transaction |
US10783576B1 (en) | 2019-03-24 | 2020-09-22 | Apple Inc. | User interfaces for managing an account |
US10860199B2 (en) | 2016-09-23 | 2020-12-08 | Apple Inc. | Dynamically adjusting touch hysteresis based on contextual data |
US10909524B2 (en) | 2018-06-03 | 2021-02-02 | Apple Inc. | User interfaces for transfer accounts |
US11074572B2 (en) | 2016-09-06 | 2021-07-27 | Apple Inc. | User interfaces for stored-value accounts |
US11100498B2 (en) | 2018-06-03 | 2021-08-24 | Apple Inc. | User interfaces for transfer accounts |
US11103161B2 (en) | 2018-05-07 | 2021-08-31 | Apple Inc. | Displaying user interfaces associated with physical activities |
US11169830B2 (en) | 2019-09-29 | 2021-11-09 | Apple Inc. | Account management user interfaces |
US20220076350A1 (en) * | 2020-09-09 | 2022-03-10 | Toshiba Tec Kabushiki Kaisha | Accounting apparatus, registration apparatus, and control method |
US11477609B2 (en) | 2019-06-01 | 2022-10-18 | Apple Inc. | User interfaces for location-related communications |
US11481094B2 (en) | 2019-06-01 | 2022-10-25 | Apple Inc. | User interfaces for location-related communications |
US20220374864A1 (en) * | 2019-11-04 | 2022-11-24 | Visa International Service Association | Method and System for Auto Filling of Payment Card Information in a Web Application |
US11580608B2 (en) | 2016-06-12 | 2023-02-14 | Apple Inc. | Managing contact information for communication applications |
US11681537B2 (en) | 2019-09-29 | 2023-06-20 | Apple Inc. | Account management user interfaces |
US11861648B2 (en) | 2012-12-14 | 2024-01-02 | Google Llc | Loyalty account identification |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2016081648A1 (en) * | 2014-11-18 | 2016-05-26 | Google Inc. | Automatically communicating user device data to a transaction computing system |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020062249A1 (en) * | 2000-11-17 | 2002-05-23 | Iannacci Gregory Fx | System and method for an automated benefit recognition, acquisition, value exchange, and transaction settlement system using multivariable linear and nonlinear modeling |
US20090037275A1 (en) * | 2007-08-03 | 2009-02-05 | Pollio Michael J | Consolidated membership/rewards card system |
US20120253914A1 (en) * | 2011-03-29 | 2012-10-04 | Visa International Service Association | Universal loyalty program device |
US8561894B1 (en) * | 2010-10-20 | 2013-10-22 | Dynamics Inc. | Powered cards and devices designed, programmed, and deployed from a kiosk |
Family Cites Families (50)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5704046A (en) | 1996-05-30 | 1997-12-30 | Mastercard International Inc. | System and method for conducting cashless transactions |
US6061660A (en) | 1997-10-20 | 2000-05-09 | York Eggleston | System and method for incentive programs and award fulfillment |
EP1182599A1 (en) | 2000-07-26 | 2002-02-27 | Transmedia Network, Inc. | System and method for providing consumer rewards |
US7398225B2 (en) | 2001-03-29 | 2008-07-08 | American Express Travel Related Services Company, Inc. | System and method for networked loyalty program |
US20020082920A1 (en) | 2000-11-17 | 2002-06-27 | Kermit Austin | System and methods for providing a multi-merchant loyalty program |
FR2818413B1 (en) | 2000-12-20 | 2006-06-23 | Maximiles | INTERNET LOYALTY SYSTEMS AND METHODS |
US20020133400A1 (en) | 2001-03-13 | 2002-09-19 | Boomerangmarketing.Com Incorporated | Systems and methods for internet reward service |
US20060053056A1 (en) | 2001-03-29 | 2006-03-09 | American Express Marketing & Development Corporati | Card member discount system and method |
US7993197B2 (en) | 2001-08-10 | 2011-08-09 | Igt | Flexible loyalty points programs |
US7606730B2 (en) | 2002-06-25 | 2009-10-20 | American Express Travel Relate Services Company, Inc. | System and method for a multiple merchant stored value card |
US8626577B2 (en) | 2002-09-13 | 2014-01-07 | Visa U.S.A | Network centric loyalty system |
US20040128197A1 (en) | 2002-10-23 | 2004-07-01 | Vayusa, Inc. | System and method of generating, distributing, and/or redeeming promotional offers using electronic devices |
KR100974811B1 (en) * | 2003-01-23 | 2010-08-10 | 주식회사 비즈모델라인 | Method for Exchanging Loyalty by Using Smart Card |
US20040249710A1 (en) | 2003-05-16 | 2004-12-09 | David Smith | Methods and apparatus for implementing loyalty programs using portable electronic data storage devices |
US20040111360A1 (en) | 2003-07-14 | 2004-06-10 | David Albanese | System and method for personal and business information exchange |
FI20045376A (en) | 2004-03-05 | 2005-09-06 | Osuma Finland Oy | Loyalty cards and devices for the same |
JP2007531123A (en) | 2004-03-26 | 2007-11-01 | シティコープ クレジット サービシィーズ インコーポレイテッド | Centralized management method and system for a plurality of reward programs |
US20130054470A1 (en) | 2010-01-08 | 2013-02-28 | Blackhawk Network, Inc. | System for Payment via Electronic Wallet |
US20050234789A1 (en) | 2004-04-14 | 2005-10-20 | Czyzewski Nathan T | Systems, methods and computer readable media for providing and managing balance transfer accounts |
KR101079859B1 (en) * | 2004-08-21 | 2011-11-04 | 주식회사 다음커뮤니케이션 | A system for providing unified payment management service and a method thereof |
WO2006078750A2 (en) | 2005-01-18 | 2006-07-27 | Isaac Mendelovich | Method for managing consumer accounts and transactions |
US20060224454A1 (en) | 2005-03-31 | 2006-10-05 | Synergy World, Inc. | Tracking merchant specific reward credits and balances in a multi merchant environment utilizing one card or account number |
US9558505B2 (en) | 2006-07-18 | 2017-01-31 | American Express Travel Related Services Company, Inc. | System and method for prepaid rewards |
WO2008086299A2 (en) | 2007-01-08 | 2008-07-17 | Skaf Mazen A | System and method for tracking and rewarding users |
US8221244B2 (en) | 2007-08-14 | 2012-07-17 | John B. French | Table with sensors and smart card holder for automated gaming system and gaming cards |
US20110270720A1 (en) | 2007-09-07 | 2011-11-03 | Manohar Enterprises, Inc. | Bank balance funds check and negative balance controls for enterprise resource planning systems |
US20100287039A1 (en) | 2007-11-14 | 2010-11-11 | Telles Marco A | Unified loyalty program media |
WO2009143419A1 (en) | 2008-05-22 | 2009-11-26 | Total System Services, Inc. | System and method for providing a product-based coupon card account |
US20090299844A1 (en) | 2008-05-29 | 2009-12-03 | Kroger Personal Finance | Prepaid reloadable electronic transaction cards with loyalty program |
US20100042517A1 (en) * | 2008-08-12 | 2010-02-18 | The Westem Union Company | Universal loyalty systems and methods |
US20100114661A1 (en) | 2008-11-05 | 2010-05-06 | American Express Travel Related Sevices Company, Inc. | Implementing a Promotional Campaign Across a Plurality of Rewards Programs |
US20100125490A1 (en) | 2008-11-14 | 2010-05-20 | Microsoft Corporation | Social network referral coupons |
US20100123012A1 (en) * | 2008-11-18 | 2010-05-20 | Michael Kaperst | Unitary membership card |
AU2010204567A1 (en) | 2009-01-15 | 2011-08-11 | Visa U.S.A. Inc. | Incentives associated with linked financial accounts |
US20110082731A1 (en) | 2009-10-07 | 2011-04-07 | Concept Shopping, Inc. | Targeted, Deferred Redemption Coupon System |
US8616441B2 (en) | 2009-12-31 | 2013-12-31 | First Data Corporation | Systems and methods for processing a transaction associated with a contactless transaction card |
US9367834B2 (en) | 2010-01-22 | 2016-06-14 | Iii Holdings 1, Llc | Systems, methods, and computer products for processing payments using a proxy card |
US20110246284A1 (en) | 2010-04-01 | 2011-10-06 | Gary Chaikin | Systems and Methods for Adding Functionality to Merchant Sales and Facilitating Data Collection. |
US20110270665A1 (en) | 2010-04-29 | 2011-11-03 | Visa U.S.A. | Expiring Virtual Gift Card Statement Credit Exchange for Loyalty Reward |
US8150844B2 (en) | 2010-08-18 | 2012-04-03 | Facebook, Inc. | Location ranking using social graph information |
US8939357B1 (en) * | 2010-12-03 | 2015-01-27 | Excentus Corporation | System and method for combining disparate commercial transactions under a single identification mechanism |
US20120166270A1 (en) | 2010-12-23 | 2012-06-28 | Apriva, Llc | System and device for facilitating mobile enrollment and participation in a loyalty campaign |
US10235688B2 (en) | 2010-12-24 | 2019-03-19 | First Data Corporation | Web and mobile device advertising |
WO2012115960A1 (en) | 2011-02-22 | 2012-08-30 | Marqeta, Inc. | System and method for providing a user with a single payment card on which prepaid/or reward balances are tracked for multiple merchants |
US20120239474A1 (en) | 2011-03-18 | 2012-09-20 | Bank Of America Corporation | Prepaid card rewards |
RU2014100969A (en) * | 2011-06-15 | 2015-07-20 | Реуорди Лтд. | BUYER LOYALTY SYSTEM |
US20130046604A1 (en) | 2011-08-17 | 2013-02-21 | Bank Of America Corporation | Virtual loyalty card program |
US20130226686A1 (en) * | 2012-02-28 | 2013-08-29 | Bank Of America Corporation | Customer loyalty identification matching |
US20140172533A1 (en) | 2012-12-14 | 2014-06-19 | Google Inc. | Loyalty account identification |
US20140257958A1 (en) | 2013-03-05 | 2014-09-11 | Google Inc. | Merchant incentive programs on proxy card systems |
-
2012
- 2012-12-14 US US13/715,543 patent/US20140172533A1/en not_active Abandoned
-
2013
- 2013-12-16 WO PCT/US2013/075512 patent/WO2014093993A1/en active Application Filing
-
2017
- 2017-08-02 US US15/667,215 patent/US20170330216A1/en not_active Abandoned
-
2020
- 2020-08-17 US US16/995,578 patent/US11861648B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020062249A1 (en) * | 2000-11-17 | 2002-05-23 | Iannacci Gregory Fx | System and method for an automated benefit recognition, acquisition, value exchange, and transaction settlement system using multivariable linear and nonlinear modeling |
US20090037275A1 (en) * | 2007-08-03 | 2009-02-05 | Pollio Michael J | Consolidated membership/rewards card system |
US8561894B1 (en) * | 2010-10-20 | 2013-10-22 | Dynamics Inc. | Powered cards and devices designed, programmed, and deployed from a kiosk |
US20120253914A1 (en) * | 2011-03-29 | 2012-10-04 | Visa International Service Association | Universal loyalty program device |
Cited By (69)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9064252B2 (en) * | 2005-10-11 | 2015-06-23 | National Payment Card Association | Payment system and methods |
US10671987B2 (en) * | 2007-06-22 | 2020-06-02 | Ncr Corporation | System and method for interacting with a self-service terminal |
US11861648B2 (en) | 2012-12-14 | 2024-01-02 | Google Llc | Loyalty account identification |
US11316968B2 (en) | 2013-10-30 | 2022-04-26 | Apple Inc. | Displaying relevant user interface objects |
US10250735B2 (en) | 2013-10-30 | 2019-04-02 | Apple Inc. | Displaying relevant user interface objects |
US10972600B2 (en) | 2013-10-30 | 2021-04-06 | Apple Inc. | Displaying relevant user interface objects |
US10748153B2 (en) | 2014-05-29 | 2020-08-18 | Apple Inc. | User interface for payments |
US10043185B2 (en) | 2014-05-29 | 2018-08-07 | Apple Inc. | User interface for payments |
US10902424B2 (en) | 2014-05-29 | 2021-01-26 | Apple Inc. | User interface for payments |
US10482461B2 (en) | 2014-05-29 | 2019-11-19 | Apple Inc. | User interface for payments |
US10438205B2 (en) | 2014-05-29 | 2019-10-08 | Apple Inc. | User interface for payments |
US10796309B2 (en) | 2014-05-29 | 2020-10-06 | Apple Inc. | User interface for payments |
US10977651B2 (en) | 2014-05-29 | 2021-04-13 | Apple Inc. | User interface for payments |
US11836725B2 (en) | 2014-05-29 | 2023-12-05 | Apple Inc. | User interface for payments |
US10282727B2 (en) | 2014-05-29 | 2019-05-07 | Apple Inc. | User interface for payments |
US10066959B2 (en) | 2014-09-02 | 2018-09-04 | Apple Inc. | User interactions for a mapping application |
US11733055B2 (en) | 2014-09-02 | 2023-08-22 | Apple Inc. | User interactions for a mapping application |
US10914606B2 (en) | 2014-09-02 | 2021-02-09 | Apple Inc. | User interactions for a mapping application |
US10255595B2 (en) | 2015-02-01 | 2019-04-09 | Apple Inc. | User interface for payments |
US10024682B2 (en) | 2015-02-13 | 2018-07-17 | Apple Inc. | Navigation user interface |
US10026094B2 (en) | 2015-06-05 | 2018-07-17 | Apple Inc. | User interface for loyalty accounts and private label accounts |
US10990934B2 (en) | 2015-06-05 | 2021-04-27 | Apple Inc. | User interface for loyalty accounts and private label accounts for a wearable device |
US10600068B2 (en) | 2015-06-05 | 2020-03-24 | Apple Inc. | User interface for loyalty accounts and private label accounts |
US20160358199A1 (en) * | 2015-06-05 | 2016-12-08 | Apple Inc. | User interface for loyalty accounts and private label accounts |
US10332079B2 (en) | 2015-06-05 | 2019-06-25 | Apple Inc. | User interface for loyalty accounts and private label accounts for a wearable device |
US11321731B2 (en) | 2015-06-05 | 2022-05-03 | Apple Inc. | User interface for loyalty accounts and private label accounts |
US11783305B2 (en) | 2015-06-05 | 2023-10-10 | Apple Inc. | User interface for loyalty accounts and private label accounts for a wearable device |
US11734708B2 (en) | 2015-06-05 | 2023-08-22 | Apple Inc. | User interface for loyalty accounts and private label accounts |
US9940637B2 (en) * | 2015-06-05 | 2018-04-10 | Apple Inc. | User interface for loyalty accounts and private label accounts |
US9965754B2 (en) * | 2015-06-08 | 2018-05-08 | Google Llc | Point of sale terminal geolocation |
US10713635B2 (en) | 2015-06-08 | 2020-07-14 | Google Llc | Point of sale terminal geolocation |
US20160358144A1 (en) * | 2015-06-08 | 2016-12-08 | Google Inc. | Point Of Sale Terminal Geolocations |
US11481769B2 (en) | 2016-06-11 | 2022-10-25 | Apple Inc. | User interface for transactions |
US10621581B2 (en) | 2016-06-11 | 2020-04-14 | Apple Inc. | User interface for transactions |
US11580608B2 (en) | 2016-06-12 | 2023-02-14 | Apple Inc. | Managing contact information for communication applications |
US11922518B2 (en) | 2016-06-12 | 2024-03-05 | Apple Inc. | Managing contact information for communication applications |
US11074572B2 (en) | 2016-09-06 | 2021-07-27 | Apple Inc. | User interfaces for stored-value accounts |
US10860199B2 (en) | 2016-09-23 | 2020-12-08 | Apple Inc. | Dynamically adjusting touch hysteresis based on contextual data |
US11144947B2 (en) * | 2016-12-27 | 2021-10-12 | Paypal, Inc. | Managing user loyalty groups at point-of-sale accesses |
US10417656B2 (en) * | 2016-12-27 | 2019-09-17 | Paypal, Inc. | Managing user loyalty groups at point-of-sale accesses |
WO2018165763A1 (en) * | 2017-03-17 | 2018-09-20 | Royal Bank Of Canada | Systems and methods for hybrid blockchain platform |
CN111465956A (en) * | 2017-04-24 | 2020-07-28 | 马克西姆.维塔利耶维奇.别克涅夫 | Method for executing payment transaction |
US20190034916A1 (en) * | 2017-07-25 | 2019-01-31 | Mastercard International Incorporated | Electronic system and method for managing loyalty account identifiers |
US10872256B2 (en) | 2017-09-09 | 2020-12-22 | Apple Inc. | Implementation of biometric authentication |
US10783227B2 (en) | 2017-09-09 | 2020-09-22 | Apple Inc. | Implementation of biometric authentication |
US10395128B2 (en) | 2017-09-09 | 2019-08-27 | Apple Inc. | Implementation of biometric authentication |
US10410076B2 (en) | 2017-09-09 | 2019-09-10 | Apple Inc. | Implementation of biometric authentication |
US10521579B2 (en) | 2017-09-09 | 2019-12-31 | Apple Inc. | Implementation of biometric authentication |
US11765163B2 (en) | 2017-09-09 | 2023-09-19 | Apple Inc. | Implementation of biometric authentication |
US11386189B2 (en) | 2017-09-09 | 2022-07-12 | Apple Inc. | Implementation of biometric authentication |
US11393258B2 (en) | 2017-09-09 | 2022-07-19 | Apple Inc. | Implementation of biometric authentication |
WO2019077346A1 (en) * | 2017-10-17 | 2019-04-25 | Payment Loyalty Limited | Improved systems and methods for delivering loyalty incentives |
US11103161B2 (en) | 2018-05-07 | 2021-08-31 | Apple Inc. | Displaying user interfaces associated with physical activities |
US11100498B2 (en) | 2018-06-03 | 2021-08-24 | Apple Inc. | User interfaces for transfer accounts |
US10909524B2 (en) | 2018-06-03 | 2021-02-02 | Apple Inc. | User interfaces for transfer accounts |
US11900355B2 (en) | 2018-06-03 | 2024-02-13 | Apple Inc. | User interfaces for transfer accounts |
US11514430B2 (en) | 2018-06-03 | 2022-11-29 | Apple Inc. | User interfaces for transfer accounts |
US11328352B2 (en) | 2019-03-24 | 2022-05-10 | Apple Inc. | User interfaces for managing an account |
US11669896B2 (en) | 2019-03-24 | 2023-06-06 | Apple Inc. | User interfaces for managing an account |
US11688001B2 (en) | 2019-03-24 | 2023-06-27 | Apple Inc. | User interfaces for managing an account |
US10783576B1 (en) | 2019-03-24 | 2020-09-22 | Apple Inc. | User interfaces for managing an account |
US11610259B2 (en) | 2019-03-24 | 2023-03-21 | Apple Inc. | User interfaces for managing an account |
US10659405B1 (en) | 2019-05-06 | 2020-05-19 | Apple Inc. | Avatar integration with multiple applications |
US11477609B2 (en) | 2019-06-01 | 2022-10-18 | Apple Inc. | User interfaces for location-related communications |
US11481094B2 (en) | 2019-06-01 | 2022-10-25 | Apple Inc. | User interfaces for location-related communications |
US11681537B2 (en) | 2019-09-29 | 2023-06-20 | Apple Inc. | Account management user interfaces |
US11169830B2 (en) | 2019-09-29 | 2021-11-09 | Apple Inc. | Account management user interfaces |
US20220374864A1 (en) * | 2019-11-04 | 2022-11-24 | Visa International Service Association | Method and System for Auto Filling of Payment Card Information in a Web Application |
US20220076350A1 (en) * | 2020-09-09 | 2022-03-10 | Toshiba Tec Kabushiki Kaisha | Accounting apparatus, registration apparatus, and control method |
Also Published As
Publication number | Publication date |
---|---|
US20170330216A1 (en) | 2017-11-16 |
US20210035147A1 (en) | 2021-02-04 |
US11861648B2 (en) | 2024-01-02 |
WO2014093993A1 (en) | 2014-06-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11861648B2 (en) | Loyalty account identification | |
US11948143B2 (en) | Automatically communicating user device data to a transaction computing system | |
US10949819B2 (en) | Managing devices associated with a digital wallet account | |
US20200234270A1 (en) | Selecting a Preferred Payment Instrument | |
KR101943562B1 (en) | Dynamic alteration of track data | |
CN107369015B (en) | Processing payment transactions without a secure element | |
US20140095385A1 (en) | Selecting merchants for automatic payments | |
US20140257958A1 (en) | Merchant incentive programs on proxy card systems | |
US20140351132A1 (en) | Returns handling in a prepaid architecture | |
US20160132876A1 (en) | Automatic closed loop payment redemption | |
US10275766B2 (en) | Encrypting financial account numbers such that every decryption attempt results in valid account numbers | |
US20190354960A1 (en) | Managing user membership accounts |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: GOOGLE INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ANDREWS, MARK WILLIAM;HUNG, RICHARD TSUWEN;DUA, ROBIN;AND OTHERS;SIGNING DATES FROM 20121207 TO 20121213;REEL/FRAME:029542/0230 |
|
AS | Assignment |
Owner name: GOOGLE LLC, CALIFORNIA Free format text: CHANGE OF NAME;ASSIGNOR:GOOGLE INC.;REEL/FRAME:044129/0001 Effective date: 20170929 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |