WO2022074416A1 - Cartes, dispositifs, systèmes et procédés destinés à la sélection de fonctionnalités de paiement avancées - Google Patents

Cartes, dispositifs, systèmes et procédés destinés à la sélection de fonctionnalités de paiement avancées Download PDF

Info

Publication number
WO2022074416A1
WO2022074416A1 PCT/IB2020/000934 IB2020000934W WO2022074416A1 WO 2022074416 A1 WO2022074416 A1 WO 2022074416A1 IB 2020000934 W IB2020000934 W IB 2020000934W WO 2022074416 A1 WO2022074416 A1 WO 2022074416A1
Authority
WO
WIPO (PCT)
Prior art keywords
card
payment
user
information
transaction
Prior art date
Application number
PCT/IB2020/000934
Other languages
English (en)
Inventor
Jeffrey D. Mullen
Original Assignee
Dynamics Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Dynamics Inc. filed Critical Dynamics Inc.
Priority to PCT/IB2020/000934 priority Critical patent/WO2022074416A1/fr
Publication of WO2022074416A1 publication Critical patent/WO2022074416A1/fr

Links

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F7/00—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
    • G07F7/08—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means
    • G07F7/0806—Details of the card
    • G07F7/0853—On-card keyboard means
    • 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/08—Payment architectures
    • G06Q20/20—Point-of-sale [POS] network systems
    • G06Q20/202—Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR
    • 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/08—Payment architectures
    • G06Q20/20—Point-of-sale [POS] network systems
    • G06Q20/204—Point-of-sale [POS] network systems comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit
    • 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/322—Aspects of commerce using mobile devices [M-devices]
    • 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/327—Short range or proximity payments by means of M-devices
    • G06Q20/3274—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being displayed on the M-device
    • 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/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/341—Active cards, i.e. cards including their own processing means, e.g. including an IC or chip
    • G06Q20/3415—Cards acting autonomously as pay-media
    • 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/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/352—Contactless payments by cards
    • 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/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/353—Payments by cards read by M-devices
    • 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/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
    • 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
    • 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/0222—During e-commerce, i.e. online transactions
    • 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/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0631—Item recommendations
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F7/00—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
    • G07F7/08—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means
    • G07F7/0806—Details of the card
    • G07F7/0813—Specific details related to card security
    • G07F7/0826—Embedded security module
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F7/00—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
    • G07F7/08—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means
    • G07F7/0806—Details of the card
    • G07F7/0833—Card having specific functional components
    • G07F7/084—Additional components relating to data transfer and storing, e.g. error detection, self-diagnosis
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F7/00—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
    • G07F7/08—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means
    • G07F7/0806—Details of the card
    • G07F7/0846—On-card display means

Definitions

  • This invention relates to magnetic cards, devices and payment systems.
  • Systems and methods are provided for allowing a user to select an additional service to be performed in addition to the payment of goods with a payment card and/or other device (e.g., a mobile telephonic device, a tablet computer device, and/or other electronic device).
  • a "card” may be used to denote powered cards, non-powered cards and other devices (e.g., powered or non-powered electronic devices, for example, computing devices).
  • a card may include one or more buttons.
  • a user may associate an additional service to a button of a card at any time.
  • information indicative of the button the user selected may be passed to a point-of-sale system with a user's payment information.
  • Such data may be, for example, communicated through a merchant acquirer's network to a processing facility.
  • the processing facility may, for example, authorize a payment transaction and forward the information indicative of the button a user selected and the identity of a user to a remote facility.
  • a remote facility may, for example, forward at least some of such information, as well as additional information, to a third party service provider such that the third party service provider enacts the additional feature desired by the user.
  • Such an additional feature may include, for example, earning and/or using a coupon provided by a coupon provider, the addition of value to a coupon by a retailer acting as an application provider, earning of a random reward from a manufacturer, and/or the like.
  • Selection of a feature may be provided, for example, by a Graphical User Interface (GUI) provided on a computing device (e.g., a mobile telephonic device) as a software and/or hardware application for that device, and/or via the internet or an intranet through a web browser.
  • GUI Graphical User Interface
  • a computing device e.g., a mobile telephonic device
  • Such a selection may be provided with a non- powered card such that a single feature may be associated with a non-powered card for a period of time.
  • Such a selection may be associated to an option (e.g., a button) on a powered card or other device (e.g., a mobile telephonic device) such that the user may associate different features with different options (e.g., different buttons).
  • a user may receive a card (e.g., a powered card, non-powered card and/or other device) in the mail and use his/her web browser to associate different additional features to different buttons.
  • the user may then utilize the card in a store and press a button in order to select that feature.
  • a card may download information (e.g., via a wireless communication such as a light and/or electromagnetic communication) such that the card, and/or other device, displays information next to an option indicative of the feature (e.g., "Redeem LivingSocial Voucher," "Facebook Like").
  • no download may be provided and no additional information may be displayed such that a user's card, and/or other device, includes a generic descriptor (e.g., "credit” and “feature,” or “feature 1" and “feature 2,” or “debit” and “feature 1” and “feature [0009]
  • a remote facility may also receive additional information than just a user identifier and information indicative of the option selected by a user (or that the user made a payment).
  • Such additional information may be, for example, the type of merchant (e.g., a retail merchant or a gas merchant), the location of a merchant (e.g., the zip code of a merchant), the type of transaction (e.g., online or in-store purchase), the name of the merchant (e.g., "Amazon.com,” or "Walmart"), the amount of the transaction (e.g., $10.25), and any other information.
  • a remote facility may forward such information to a third party service provider in addition to information generated by the remote facility (e.g., a second user identifier such that different identifiers are used with the facility sending payment information and the third party service provider).
  • a feature/payment method ecosystem may be provided in which a development kit is available for third parties to develop applications for payment cards or other devices.
  • a GUI may be provided where a user can select different third party applications to be associated with one or more user payment methods.
  • the third party applications may be approved by an administrator and/or an approval signature flow before being accessible by a GUI.
  • Different categories of third party applications may be provided on the GUI (e.g., a coupon category, a check-in category, a games category, a financial management tools category).
  • the development kit may provide the ability for a third party service provider to, for example, receive user identification numbers and other information, (e.g., merchant name and location) and provide particular information (e.g., within a period of time) to a remote facility.
  • Information received from a third party service provider may include, for example, information indicative that the user was properly identified and a service was performed (e.g., "check-in completed," "information added to financial management service.”). Such information may be provided back to an issuing bank, processor, or other service provider such that the information may be displayed on a user's billing statement. Additional information may also be provided that may change the way a transaction is authorized or settled.
  • Additional information received from a third party may be utilized to change the way a transaction is authorized or settled.
  • a third party may provide a user with the ability to pre-purchase a voucher to a particular store (e.g., a particular barber in a particular zip code).
  • a user may associate this third party service to a button on the user's card.
  • a user may purchase a service at a barber multiple times during a year on the user's credit account. The user may, at one such purchase, press the button associated with the desire to use the third party service and redeem a voucher the user already purchased or acquired.
  • Information indicative of the user's desire to utilize such a service may be communicated to a point- of-sale terminal via a communications device located on the card (e.g., a dynamic magnetic stripe communications device, an RFID antenna, an exposed IC chip (e.g., an EMV chip, or any other communications device).
  • the transaction may be authorized using the user's payment account if, for example, the user has enough funds associated with that account (e.g., a credit or debit account).
  • the third party service provider may then determine the user had a pre-paid voucher for the transaction and may return to the card issuer, processor, and/or other party information indicative that the user's bill is to be adjusted by the amount of the voucher.
  • a user's bill may show a statement credit in the amount of the voucher.
  • a remote facility may perform such a data exchange as well as any associated value exchange.
  • the remote facility may, for a fee (e.g., a percentage of a transaction or a fixed fee), provide value from the third party service provider to the card issuer or processor (e.g., via an ACH or other type of monetary transaction).
  • the remote facility may provide the desired value to the card issuer, processor, and/or other party and demand the associated value be paid to the remote facility by the third party service provider within a period of time (e.g., three days).
  • Information provided by a third party service provider to a remote facility may include an identifier indicative of the third party service provider, an identifier indicative of the user, an identifier indicative of the type of service provided by the third party service provider, an identifier indicative of the transaction with which further action by the third party service provider is desired, an amount of a post-statement credit that is to be applied for a particular transaction, and amount of a post-settlement credit that is to be applied for a particular transaction, an amount of a pre-settlement credit that is to be applied for a particular transaction, an amount of a credit that is to be applied during an authorization, an additional fee to be added to a statement for an additional service (e.g., a fee-based financial management tool service), and any other information desired by the third party service provider, processor, card issuer, remote facility, device provider, and/or any other entity (e.g., a card network).
  • a card network e.g., a card network
  • Information indicative of a button press, and/or use of a card, that triggers a feature may be provided in a payment message utilized at authorization or at settlement. Furthermore, the service provider may return information in a period of time that permits actions to be performed pre-authorization and/or pre- settlement.
  • the payment actions may be determined, for example, via a user interaction with the card. Particularly, for example, a user may press a button on the card, from a group of buttons, the button being associated with the third party feature.
  • the third party feature may be unique from the features provided to the user via the third party's non-payment card or device services. Accordingly, a user may obtain the benefit of the whimsical and festive nature of a unique feature every time the user makes a payment.
  • Information indicative of feature selection may be provided, for example, via an output device operable to be read by a card reader.
  • the feature selection may be communicated by a dynamic magnetic stripe communications device, an RFID antenna, an exposed IC chip, or any other type of output device.
  • a display may be provided on the card and a user selection may cause a particular number (e.g., a particular code) to be displayed on the card.
  • a code may be entered into a text box on a website at checkout and may be representative of the user's desired feature.
  • the feature may be communicated to a remote server such that the feature may be performed in the third party service on behalf of the user.
  • the code may additionally provide the benefits of a security code and may be entered with a payment card number (e.g., a credit or debit card number) at online or in-store checkout. If a code is not representative of a feature, for example, a default feature may be provided.
  • a payment card number e.g., a credit or debit card number
  • Rewards may be awarded based on the amount of a purchase.
  • Such rewards may be associated with a third party service or a card issuer, card provider, or other entity.
  • a coupon may be awarded by an application provider at every purchase instead of a card issuer providing an amount of points, miles, or cashback to a user.
  • a user may earn both rewards from a card issuer as well as rewards from a third party service provider.
  • a user may select, via, for example, physical buttons on the card or virtual buttons on a capacitive-sensitive display of a mobile telephonic device, the type of feature the user desires.
  • Multiple features may be provided from a particular third party service provider.
  • a coupon provider may provide a feature associated with a coupon and another feature associated with another coupon.
  • a card may include a dynamic magnetic communications device.
  • a dynamic magnetic communications device may take the form of a magnetic encoder and/or a magnetic emulator.
  • a magnetic encoder may change the information located on a magnetic medium such that a magnetic stripe reader may read changed magnetic information from the magnetic medium.
  • a magnetic emulator may generate electromagnetic fields that directly communicate data to a magnetic stripe reader. Such a magnetic emulator may communicate data serially to a read-head of the magnetic stripe reader.
  • All, or substantially all, of the front as well as the back of a card may be a display (e.g., bi-stable, non bi-stable, LCD, LED, or electrochromic display).
  • Electrodes of a display may be coupled to one or more capacitive touch sensors such that a display may be provided as a touch-screen display. Any type of touch- screen display may be utilized. Such touch-screen displays may be operable of determining multiple points of touch.
  • a barcode may be displayed across all, or substantially all, of a surface of a card. In doing so, computer vision equipment such as barcode readers may be less susceptible to errors in reading a displayed barcode.
  • a card may include a number of output devices to output dynamic information.
  • a card may include one or more RFIDs and/or IC chips to communicate to one or more RFID readers or IC chip readers, respectively.
  • a card may include three or more different types of output devices.
  • a card may include devices to receive information.
  • an RFID and IC chip may both receive information and communicate information to an RFID and IC chip reader, respectively.
  • a device for receiving wireless information signals may be provided.
  • a light sensing device and/or sound sensing device may be utilized to receive information wirelessly.
  • a card may include a central processor that communicates data through one or more output devices simultaneously (e.g., an RFID, IC chip, and a dynamic magnetic stripe communications device).
  • the central processor may receive information from one or more input devices simultaneously (e.g., an RFID, IC chip, dynamic magnetic stripe devices, light sensing device, and a sound sensing device).
  • a processor may be coupled to surface contacts such that the processor may perform the processing capabilities of, for example, an EMV chip.
  • the processor may be laminated over and not exposed such that such a processor is not exposed on the surface of the card.
  • a card may be provided with a button in which the activation of the button causes a code to be communicated through a dynamic magnetic stripe communications device (e.g., the subsequent time a read- head detector on the card detects a read-head).
  • the code may be indicative of, for example, a feature (e.g., a payment feature).
  • the code may be received by the card via manual input (e.g., onto buttons of the card) or via a wireless transmission (e.g., via light, electromagnetic communications, sound, or other wireless signals).
  • a code may be communicated from a webpage (e.g., via light and/or sound) to a card.
  • a card may include a display such that a received code may be visually displayed to a user.
  • the user may be provided with a way to select, and use, the code via both an in-store setting (e.g., via a magnetic stripe reader) or an online setting (e.g., by reading the code from a display and entering the code into a text box on a checkout page of an online purchase transaction).
  • an in-store setting e.g., via a magnetic stripe reader
  • an online setting e.g., by reading the code from a display and entering the code into a text box on a checkout page of an online purchase transaction.
  • a remote server such as a payment authorization server, may receive the code and may process a payment differently based on the code received.
  • a code may be a security code to authorize a purchase transaction.
  • a code may provide a payment feature such that a purchase may be made with points, debit, credit, installment payments, and/or deferred payments via a single payment account number (e.g., a credit card number) to identify a user and a payment feature code to select the type of payment a user desires to utilize.
  • a dynamic magnetic stripe communications device may include a magnetic emulator that comprises an inductor (e.g., a coil). Current may be provided through this coil to create an electromagnetic field operable to communicate with the read-head of a magnetic stripe reader.
  • the drive circuit may vary the amount of current travelling through the coil such that a track of magnetic stripe data may be communicated to a read-head of a magnetic stripe reader.
  • a switch e.g., a transistor
  • F2F frequency/double-frequency
  • Electronics may be embedded between two layers of a polymer (e.g., a PVC or non-PVC polymer).
  • a polymer e.g., a PVC or non-PVC polymer
  • One or more liquid polymers may be provided between these two layers.
  • the liquid polymer(s) may, for example, be hardened via a reaction between the polymers (or other material), temperature, and/or via light (e.g., an ultraviolet or blue spectrum light) such that the electronics become embedded between the two layers of the polymer and a card is formed.
  • a payment card or other device may receive information indicative of a feature desired to be added by a user.
  • the payment card may communicate information indicative of the feature with payment card data associated with the card or a user selection.
  • the payment data and feature information may be routed, for example, to an authorization server.
  • the authorization server may authorize payment and, based on the authorized payment, communicate the feature information to a remote server.
  • the remote server may utilize this remote information to impact a third party service.
  • the feature information may, for example, be routed before the payment card data reaches an authorization server.
  • charge backs for a purchase associated with a reward may cause the feature to be reversed or a different feature to be implemented (e.g., a removal of rewards earned at authorization).
  • the feature may be implemented at settlement upon confirmation that, for example, no chargeback was associated with the payment transaction.
  • a graphical user interface may be provided to allow users to display one or more application managers and one or more application provider interfaces.
  • the GUI may be rendered onto a display of a card (e.g., a powered card, a mobile telephonic device, an electronic tablet, a laptop computer, or a desktop computer) and may allow a user to configure features that are desired to be added by the user.
  • a card e.g., a powered card, a mobile telephonic device, an electronic tablet, a laptop computer, or a desktop computer
  • a user may, for example, associate a card with one or more third party service features using the application manager.
  • Such an application manager may be an interface to an ecosystem of applications and payment methods, where users within the ecosystem may manage which application(s) may be associated with a particular payment method (e.g., payment method card).
  • a user may alter such associations at any time.
  • the payment method Prior to associating one or more applications to a particular payment method, the payment method may be associated with one or more default applications that may be later modified by the user.
  • a GUI may be provided on an electronic device to administer one or more third party applications that facilitate the provision of coupons and/or the addition of value to coupons.
  • the coupons and/or additional value may be earned by a user upon completion of a performance metric.
  • a coupon may be selected by a user from every coupon made available by an application and/or feature provider, the coupon may be automatically determined and/or a coupon may selected by a user from a number of hidden coupons (e.g., via a virtual scratch-off).
  • an application provider may be a coupon provider that distributes coupons from a variety of retailers, a retailer and/or a collection of retailers.
  • a user of a payment method may earn a coupon and/or add value to a coupon each time the user spends a target amount of money using the powered card. Additionally and/or alternatively, a user may receive a reward randomly from a collection of rewards including coupons, virtual items and tangible items, and/or select a blank reward from among multiple blank rewards to reveal a coupon.
  • a performance metric may include, for example, a purchase with a card (e.g., a physical and/or virtual payment method card), a sequence of purchases (e.g., ten purchases), a total amount spent, and/or other metrics related to various purchasing and/or non-purchasing transactional events.
  • a card e.g., a physical and/or virtual payment method card
  • sequence of purchases e.g., ten purchases
  • total amount spent e.g., a total amount spent
  • a reward may scale based on an associated performance metric.
  • a coupon may be earned from all coupons provided by a coupon provider each time a user makes purchases meeting or exceeding a specific dollar amount. For a dollar amount exceeding the specific dollar amount, a user may instead receive multiple coupons and/or add additional value to a coupon.
  • a computing device may receive a first message including a coupon identifier of a multistage coupon, obtain a monetary value of a current stage of the multistage coupon based on the coupon identifier, and communicate a second message based on the first message, the second message indicating the monetary value of the current stage of the multistage coupon.
  • the multistage coupon may not be associated with a user. Whether a condition to awarding the monetary value is met may be determined.
  • the first message may include at least a portion of purchase transaction data, and the determination that the condition is met may be based on the at least a portion of the purchase transaction data.
  • the current stage and a stage threshold may be obtained, and a determination made as to whether the current stage is equal to or exceeds the threshold.
  • the second message may include an indication of card eligibility upon determining that the current stage is equal to or exceeds the threshold.
  • a point of sale may be obtained, and a determination made as to whether the current stage is equal to or exceeds the threshold.
  • POS terminal may receive a barcode including a payment routing identity and communicate the barcode and data associated with a purchase transaction based on the routing identity.
  • the POS terminal may receive a second barcode associated with at least one of an installment, a loyalty account, a discount and a request to pay for all or a portion of a purchase with points.
  • a wallet card device may include three buttons, a printed circuit board (PCB) antenna connectable to any cellular band, dual pressure sensors usable to determine speed of the wallet card device, a cellular chip, and a dynamic magnetic communications device usable to communicate waveforms at more than one amplitude, the wallet card device usable to dynamically change an encryption/decryption key between a payment network and the cellular chip is operable to be dynamically changed.
  • PCB printed circuit board
  • a “card” may be used to denote powered cards, non-powered cards and other devices (e.g., powered or non-powered electronic devices, for example, computing devices).
  • a card may include one or more buttons.
  • a user may associate an additional service to a button of a card at any time. At the time of purchase, information indicative of the button the user selected may be passed to a point-of-sale system with a user's payment information. Such data may be, for example, communicated through a merchant acquirer's network to a processing facility.
  • the processing facility may, for example, authorize a payment transaction and forward the information indicative of the button a user selected and the identity of a user to a remote facility.
  • a remote facility may, for example, forward at least some of such information, as well as additional information, to a third party service provider such that the third party service provider enacts the additional feature desired by the user.
  • Such an additional feature may include, for example, earning and/or using a coupon provided by a coupon provider, the addition of value to a coupon by a retailer acting as an application provider, earning of a random reward from a manufacturer, and/or the like.
  • Selection of a feature may be provided, for example, by a Graphical User Interface (GUI) provided on a computing device (e.g., a mobile telephonic device) as a software and/or hardware application for that device, and/or via the internet or an intranet through a web browser.
  • GUI Graphical User Interface
  • a computing device e.g., a mobile telephonic device
  • Such a selection may be provided with a non- powered card such that a single feature may be associated with a non-powered card for a period of time.
  • Such a selection may be associated to an option (e.g., a button) on a powered card or other device (e.g., a mobile telephonic device) such that the user may associate different features with different options (e.g., different buttons).
  • a user may receive a card (e.g., a powered card, non-powered card and/or other device) in the mail and use his/her web browser to associate different additional features to different buttons.
  • the user may then utilize the card in a store and press a button in order to select that feature.
  • a card may download information (e.g., via a wireless communication such as a light and/or electromagnetic communication) such that the card, and/or other device, displays information next to an option indicative of the feature (e.g., "Redeem LivingSocial Voucher," "Facebook Like").
  • no download may be provided and no additional information may be displayed such that a user's card, and/or other device, includes a generic descriptor (e.g., "credit” and “feature,” or “feature 1” and “feature 2,” or “debit” and “feature 1” and “feature 2").
  • a generic descriptor e.g., "credit” and “feature,” or “feature 1” and “feature 2,” or “debit” and “feature 1” and “feature 2”
  • a remote facility may also receive additional information than just a user identifier and information indicative of the option selected by a user (or that the user made a payment).
  • additional information may be, for example, the type of merchant (e.g., a retail merchant or a gas merchant), the location of a merchant (e.g., the zip code of a merchant), the type of transaction (e.g., online or in-store purchase), the name of the merchant (e.g., "Amazon.com,” or "Walmart”), the amount of the transaction (e.g., $10.25), and any other information.
  • Such a remote facility may forward such information to a third party service provider in addition to information generated by the remote facility (e.g., a second user identifier such that different identifiers are used with the facility sending payment information and the third party service provider).
  • a feature/payment method ecosystem may be provided in which a development kit is available for third parties to develop applications for payment cards or other devices.
  • a GUI may be provided where a user can select different third party applications to be associated with one or more user payment methods.
  • the third party applications may be approved by an administrator and/or an approval signature flow before being accessible by a GUI.
  • Different categories of third party applications may be provided on the GUI (e.g., a coupon category, a check-in category, a games category, a financial management tools category).
  • the development kit may provide the ability for a third party service provider to, for example, receive user identification numbers and other information, (e.g., merchant name and location) and provide particular information (e.g., within a period of time) to a remote facility.
  • Information received from a third party service provider may include, for example, information indicative that the user was properly identified and a service was performed (e.g., "check-in completed," "information added to financial management service.”). Such information may be provided back to an issuing bank, processor, or other service provider such that the information may be displayed on a user's billing statement. Additional information may also be provided that may change the way a transaction is authorized or settled.
  • Additional information received from a third party may be utilized to change the way a transaction is authorized or settled.
  • a third party may provide a user with the ability to pre-purchase a voucher to a particular store (e.g., a particular barber in a particular zip code).
  • a user may associate this third party service to a button on the user's card.
  • a user may purchase a service at a barber multiple times during a year on the user's credit account. The user may, at one such purchase, press the button associated with the desire to use the third party service and redeem a voucher the user already purchased or acquired.
  • Information indicative of the user's desire to utilize such a service may be communicated to a point- of-sale terminal via a communications device located on the card (e.g., a dynamic magnetic stripe communications device, an RFID antenna, an exposed IC chip (e.g., an EMV chip, or any other communications device).
  • a communications device located on the card e.g., a dynamic magnetic stripe communications device, an RFID antenna, an exposed IC chip (e.g., an EMV chip, or any other communications device.
  • the transaction may be authorized using the user's payment account if, for example, the user has enough funds associated with that account (e.g., a credit or debit account).
  • the third party service provider may then determine the user had a pre-paid voucher for the transaction and may return to the card issuer, processor, and/or other party information indicative that the user's bill is to be adjusted by the amount of the voucher. Before, or after, settlement occurs a user's bill may show a statement credit in the amount of the voucher.
  • a remote facility may perform such a data exchange as well as any associated value exchange. For example, the remote facility may, for a fee (e.g., a percentage of a transaction or a fixed fee), provide value from the third party service provider to the card issuer or processor (e.g., via an ACH or other type of monetary transaction).
  • the remote facility may provide the desired value to the card issuer, processor, and/or other party and demand the associated value be paid to the remote facility by the third party service provider within a period of time (e.g., three days).
  • Information provided by a third party service provider to a remote facility may include an identifier indicative of the third party service provider, an identifier indicative of the user, an identifier indicative of the type of service provided by the third party service provider, an identifier indicative of the transaction with which further action by the third party service provider is desired, an amount of a post-statement credit that is to be applied for a particular transaction, and amount of a post-settlement credit that is to be applied for a particular transaction, an amount of a pre-settlement credit that is to be applied for a particular transaction, an amount of a credit that is to be applied during an authorization, an additional fee to be added to a statement for an additional service (e.g., a fee-based financial management tool service), and any other information desired by
  • Information indicative of a button press, and/or use of a card, that triggers a feature may be provided in a payment message utilized at authorization or at settlement. Furthermore, the service provider may return information in a period of time that permits actions to be performed pre-authorization and/or pre- settlement.
  • the payment actions may be determined, for example, via a user interaction with the card. Particularly, for example, a user may press a button on the card, from a group of buttons, the button being associated with the third party feature.
  • the third party feature may be unique from the features provided to the user via the third party's non-payment card or device services. Accordingly, a user may obtain the benefit of the whimsical and festive nature of a unique feature every time the user makes a payment.
  • Information indicative of feature selection may be provided, for example, via an output device operable to be read by a card reader.
  • the feature selection may be communicated by a dynamic magnetic stripe communications device, an RFID antenna, an exposed IC chip, or any other type of output device.
  • a display may be provided on the card and a user selection may cause a particular number (e.g., a particular code) to be displayed on the card.
  • a code may be entered into a text box on a website at checkout and may be representative of the user's desired feature.
  • the feature may be communicated to a remote server such that the feature may be performed in the third party service on behalf of the user.
  • the code may additionally provide the benefits of a security code and may be entered with a payment card number (e.g., a credit or debit card number) at online or in-store checkout. If a code is not representative of a feature, for example, a default feature may be provided.
  • a payment card number e.g., a credit or debit card number
  • Rewards may be awarded based on the amount of a purchase.
  • Such rewards may be associated with a third party service or a card issuer, card provider, or other entity.
  • a coupon may be awarded by an application provider at every purchase instead of a card issuer providing an amount of points, miles, or cashback to a user.
  • a user may earn both rewards from a card issuer as well as rewards from a third party service provider.
  • a user may select, via, for example, physical buttons on the card or virtual buttons on a capacitive-sensitive display of a mobile telephonic device, the type of feature the user desires.
  • Multiple features may be provided from a particular third party service provider.
  • a coupon provider may provide a feature associated with a coupon and another feature associated with another coupon.
  • a card may include a dynamic magnetic communications device.
  • a dynamic magnetic communications device may take the form of a magnetic encoder and/or a magnetic emulator.
  • a magnetic encoder may change the information located on a magnetic medium such that a magnetic stripe reader may read changed magnetic information from the magnetic medium.
  • a magnetic emulator may generate electromagnetic fields that directly communicate data to a magnetic stripe reader. Such a magnetic emulator may communicate data serially to a read-head of the magnetic stripe reader.
  • All, or substantially all, of the front as well as the back of a card may be a display (e.g., bi-stable, non bi-stable, LCD, LED, or electrochromic display).
  • Electrodes of a display may be coupled to one or more capacitive touch sensors such that a display may be provided as a touch-screen display. Any type of touch- screen display may be utilized. Such touch-screen displays may be operable of determining multiple points of touch.
  • a barcode may be displayed across all, or substantially all, of a surface of a card. In doing so, computer vision equipment such as barcode readers may be less susceptible to errors in reading a displayed barcode.
  • a card may include a number of output devices to output dynamic information.
  • a card may include one or more RFIDs and/or IC chips to communicate to one or more RFID readers or IC chip readers, respectively.
  • a card may include three or more different types of output devices.
  • a card may include devices to receive information.
  • an RFID and IC chip may both receive information and communicate information to an RFID and IC chip reader, respectively.
  • a device for receiving wireless information signals may be provided.
  • a light sensing device and/or sound sensing device may be utilized to receive information wirelessly.
  • a card may include a central processor that communicates data through one or more output devices simultaneously (e.g., an RFID, IC chip, and a dynamic magnetic stripe communications device).
  • the central processor may receive information from one or more input devices simultaneously (e.g., an RFID, IC chip, dynamic magnetic stripe devices, light sensing device, and a sound sensing device).
  • a processor may be coupled to surface contacts such that the processor may perform the processing capabilities of, for example, an EMV chip.
  • the processor may be laminated over and not exposed such that such a processor is not exposed on the surface of the card.
  • a card may be provided with a button in which the activation of the button causes a code to be communicated through a dynamic magnetic stripe communications device (e.g., the subsequent time a read- head detector on the card detects a read-head).
  • the code may be indicative of, for example, a feature (e.g., a payment feature).
  • the code may be received by the card via manual input (e.g., onto buttons of the card) or via a wireless transmission (e.g., via light, electromagnetic communications, sound, or other wireless signals).
  • a code may be communicated from a webpage (e.g., via light and/or sound) to a card.
  • a card may include a display such that a received code may be visually displayed to a user.
  • the user may be provided with a way to select, and use, the code via both an in-store setting (e.g., via a magnetic stripe reader) or an online setting (e.g., by reading the code from a display and entering the code into a text box on a checkout page of an online purchase transaction).
  • an in-store setting e.g., via a magnetic stripe reader
  • an online setting e.g., by reading the code from a display and entering the code into a text box on a checkout page of an online purchase transaction.
  • a remote server such as a payment authorization server, may receive the code and may process a payment differently based on the code received.
  • a code may be a security code to authorize a purchase transaction.
  • a code may provide a payment feature such that a purchase may be made with points, debit, credit, installment payments, and/or deferred payments via a single payment account number (e.g., a credit card number) to identify a user and a payment feature code to select the type of payment a user desires to utilize.
  • a dynamic magnetic stripe communications device may include a magnetic emulator that comprises an inductor (e.g., a coil). Current may be provided through this coil to create an electromagnetic field operable to communicate with the read-head of a magnetic stripe reader.
  • the drive circuit may vary the amount of current travelling through the coil such that a track of magnetic stripe data may be communicated to a read-head of a magnetic stripe reader.
  • a switch e.g., a transistor
  • F2F frequency/double-frequency
  • Electronics may be embedded between two layers of a polymer (e.g., a PVC or non-PVC polymer).
  • a polymer e.g., a PVC or non-PVC polymer
  • One or more liquid polymers may be provided between these two layers.
  • the liquid polymer(s) may, for example, be hardened via a reaction between the polymers (or other material), temperature, and/or via light (e.g., an ultraviolet or blue spectrum light) such that the electronics become embedded between the two layers of the polymer and a card is formed.
  • a payment card or other device may receive information indicative of a feature desired to be added by a user.
  • the payment card may communicate information indicative of the feature with payment card data associated with the card or a user selection.
  • the payment data and feature information may be routed, for example, to an authorization server.
  • the authorization server may authorize payment and, based on the authorized payment, communicate the feature information to a remote server.
  • the remote server may utilize this remote information to impact a third party service.
  • the feature information may, for example, be routed before the payment card data reaches an authorization server.
  • charge backs for a purchase associated with a reward may cause the feature to be reversed or a different feature to be implemented (e.g., a removal of rewards earned at authorization).
  • the feature may be implemented at settlement upon confirmation that, for example, no chargeback was associated with the payment transaction.
  • a graphical user interface may be provided to allow users to display one or more application managers and one or more application provider interfaces.
  • the GUI may be rendered onto a display of a card (e.g., a powered card, a mobile telephonic device, an electronic tablet, a laptop computer, or a desktop computer) and may allow a user to configure features that are desired to be added by the user.
  • a card e.g., a powered card, a mobile telephonic device, an electronic tablet, a laptop computer, or a desktop computer
  • a user may, for example, associate a card with one or more third party service features using the application manager.
  • Such an application manager may be an interface to an ecosystem of applications and payment methods, where users within the ecosystem may manage which application(s) may be associated with a particular payment method (e.g., payment method card).
  • a user may alter such associations at any time.
  • the payment method Prior to associating one or more applications to a particular payment method, the payment method may be associated with one or more default applications that may be later modified by the user.
  • a GUI may be provided on an electronic device to administer one or more third party applications that facilitate the provision of coupons and/or the addition of value to coupons.
  • the coupons and/or additional value may be earned by a user upon completion of a performance metric.
  • a coupon may be selected by a user from every coupon made available by an application and/or feature provider, the coupon may be automatically determined and/or a coupon may selected by a user from a number of hidden coupons (e.g., via a virtual scratch-off).
  • an application provider may be a coupon provider that distributes coupons from a variety of retailers, a retailer and/or a collection of retailers.
  • a user of a payment method may earn a coupon and/or add value to a coupon each time the user spends a target amount of money using the powered card. Additionally and/or alternatively, a user may receive a reward randomly from a collection of rewards including coupons, virtual items and tangible items, and/or select a blank reward from among multiple blank rewards to reveal a coupon.
  • a performance metric may include, for example, a purchase with a card (e.g., a physical and/or virtual payment method card), a sequence of purchases (e.g., ten purchases), a total amount spent, and/or other metrics related to various purchasing and/or non-purchasing transactional events.
  • a card e.g., a physical and/or virtual payment method card
  • sequence of purchases e.g., ten purchases
  • total amount spent e.g., a total amount spent
  • a reward may scale based on an associated performance metric.
  • a coupon may be earned from all coupons provided by a coupon provider each time a user makes purchases meeting or exceeding a specific dollar amount. For a dollar amount exceeding the specific dollar amount, a user may instead receive multiple coupons and/or add additional value to a coupon.
  • a computing device may receive a first message including a coupon identifier of a multistage coupon, obtain a monetary value of a current stage of the multistage coupon based on the coupon identifier, and communicate a second message based on the first message, the second message indicating the monetary value of the current stage of the multistage coupon.
  • the multistage coupon may not be associated with a user. Whether a condition to awarding the monetary value is met may be determined.
  • the first message may include at least a portion of purchase transaction data, and the determination that the condition is met may be based on the at least a portion of the purchase transaction data.
  • a device may include memory for storing card information of a payment card, a display to display user identification information, a button to initialize the card, and by pressing the button information of the payment card may be displayed on the display.
  • the memory may store information of more than one payment card and by pressing the button again, information of a different payment card may be displayed on the display.
  • a card may include a dynamic magnetic communications device, which may take the form of a magnetic encoder or an electromagnetic generator.
  • a magnetic encoder may be utilized to modify information that is located on a magnetic medium, such that a magnetic stripe reader may then be utilized to read the modified magnetic information from the magnetic medium.
  • An electromagnetic generator for example, may be provided to generate electromagnetic fields that directly communicate data to a read-head of a magnetic stripe reader.
  • An electromagnetic generator for example, may communicate data serially to a read-head of the magnetic stripe reader.
  • An electromagnetic generator for example, may communicate data in parallel to a read-head of a magnetic stripe reader.
  • a card may include, for example, a static magnetic stripe that may be pre-programmed with magnetic information (e.g., financial account information associated with the card), which may be read by a magnetic stripe reader when the card is swiped across a read head of the magnetic stripe reader.
  • magnetic information e.g., financial account information associated with the card
  • All, or substantially all, of the front surface, as well as the rear surface, of a card may be implemented as a display (e.g., bi-stable, non bi- stable, LCD, or electrochromic display). Electrodes of a display may be coupled to one or more touch sensors, such that a display may be sensitive to touch (e.g., using a finger or a pointing device) and may be further sensitive to a location of the touch. The display may be sensitive, for example, to objects that come within a proximity of the display without actually touching the display.
  • a card may include one or more light sources (e.g., light emitting diodes (LED)).
  • LED light emitting diodes
  • One or more of such light sources may be configured according to a pattern within the card, whereby the pattern is unseen until the light sources are activated. Alternately, patterns visible on the card's surfaces (e.g., personalization indicia) may be visible, but may be highlighted when such light sources are activated.
  • a dynamic magnetic stripe communications device may be implemented on a multiple layer board (e.g., a two-layer flexible printed circuit board).
  • a coil for each track of information that is to be communicated by the dynamic magnetic stripe communications device may then be provided by including wire segments on each layer and interconnecting the wire segments through layer interconnections to create a coil.
  • a dynamic magnetic stripe communications device may include two coils such that two tracks of information may be communicated to two different read-heads included in a read-head housing of a magnetic stripe reader.
  • a dynamic magnetic communications device may include, for example, three coils such that three tracks of information may be communicated to three different read-heads included in a read-head housing of a magnetic stripe reader.
  • Input and/or output devices may be included on a card, for example, to facilitate data exchange with the card.
  • an integrated circuit IC
  • Such a chip may communicate information to a chip reader (e.g., an EMV chip reader) and/or may receive information from the chip reader (e.g., a balance remaining on a gift card) which may then be stored in a memory of the card and used for a particular purpose (e.g., lights on the card may illuminate to indicate a balance remaining on the gift card).
  • a chip reader e.g., an EMV chip reader
  • An RFID antenna or module may be included on a card, for example, to send and/or receive information between an RFID reader and the RFID included on the card.
  • One or more detectors may be provided, for example, to sense the presence of an external object, such as a person or device, which in turn, may trigger a communication sequence with the external object. Accordingly, for example, timing aspects of an information exchange between an external object and the various I/O devices implemented on a card may be determined by a processor of a card.
  • a sensed presence of an external object or device may include the type of object or device that is detected and, therefore, may then determine the type of communication that is to be used with the detected object or device.
  • a detected object may include a determination that the object is a read-head housing of a magnetic stripe reader.
  • Such an identifying detection may activate a dynamic magnetic stripe communications device so that information may be communicated (e.g., electromagnetically communicated) to the read-head of the magnetic stripe reader.
  • a static magnetic stripe may be used to provide information to the magnetic stripe reader and a detection of the magnetic stripe reader may be used for other purposes (e.g., to illuminate portions of the card so that the card holder and others in proximity to the card holder may witness the card's reaction to the detected magnetic stripe reader).
  • One or more read-head detectors may be provided on a card.
  • the one or more read-head detectors may be provided as, for example, conductive pads that may be arranged along a length of a card having a variety of shapes.
  • a property e.g., a capacitance magnitude
  • a property of one or more of the conductive pads may, for example, change in response to contact with and/or the proximity of an object.
  • a card may, for example, be swiped across a read-head of a magnetic stripe reader, such that a series of conductive pads arranged along a length of the card may be used by a processor to sequentially detect the presence of the read-head as the read-head moves in relation to the card.
  • a series of detections e.g., the capacitance magnitude of a series of conductive pads may increase and/or decrease
  • a direction of a card swipe e.g., the capacitance magnitude of a series of conductive pads may increase and/or decrease
  • a processor of the card may activate a transaction indicator (e.g., a visible or audible indicator) that is indicative of a completed transaction.
  • a processor of a card may activate one or more LEDs of one or more sets of LEDs to illuminate a feature on the card that indicates that the card has been used in a transaction.
  • a user may obtain the benefit of the whimsical and festive nature of a visible transaction indicator every time the user uses the card during a transaction.
  • activation of the one or more LEDs may be indicative of an outcome of such a transaction (e.g., the number of LEDs activated may indicate a balance left on a gift card after the transaction completes).
  • False alarm detection may be implemented to reduce occurrences of false alarms.
  • certain objects e.g., a finger
  • a processor of a card may detect, for example, a presence of a read- head housing of a magnetic stripe reader when, in fact, no read-head housing is present.
  • knowledge of, for example, a previously detected card swipe and associated direction may allow a second detection to be made, whereby a second read-head detection that is consistent with the originally detected card swipe direction may enable verification of a legitimate card swipe and, therefore, may enable a successful communication sequence with a magnetic stripe reader whose presence has been detected and verified, which may then be followed by a visible and/or an audible and/or a tactile indication that a transaction using the card has been completed.
  • One or more, for example, over 5 glow areas including a light material such as light guides that disperse light from light emitting diodes (LEDs).
  • the LEDs may be face firing or side firing, to cause glow areas to emit light.
  • Glow areas may be in the shape of logos, animals, or other thematic imagery. Glow areas may additionally or alternatively include a large number of LEDs, for example, over 100, over 150, over
  • a user may begin a transaction (e.g., insert a card into a reader), the card may perform a light show based on information received from a reader (e.g., CDOL - Card Risk Management Data Object List and/or PDOL - Processing Options Data Objects List, information utilized by artificial intelligence, hardware and/or software of a card or device) or issuer scripts received from a remote server (e.g., a financial institution).
  • the light show may be tailored to a particular event, for example, 'Happy Birthday' displayed on or near the cardholder's date of birth or 'Happy New Year' and/or a fireworks display at or near the beginning of the New Year.
  • a transaction is performed in Germany after a transaction is performed in a different country, 'Welcome to Germany!' may be displayed.
  • a display may be a variety of configurations, for example, a dot matrix display of any number of LED rows and columns (e.g., 7 rows x 24 columns).
  • One or more processors and/or controllers may be provided for the display.
  • Fast imagery may be displayed by scanning columns, for example, faster than the eye can see and/or using fewer than all the LEDs of the display (e.g., 5, 10, 15 or 20).
  • Cards or other device may provide happiness and/or joy through festive displays triggered according to any events or for no reason (randomly). For example, at the beginning of a transaction a display may be turned on, and upon approval/authorization, a different image display (e.g., a waiting symbol to a thumbs-up symbol). Displays may differ based on, for example, the venue (a different display for a gas station than a purchase at the Special Olympics). Cards and other devices may provide displays taking into consideration, for example, medical information (e.g., reduced flashing for epileptic card holders). Prizes and transactions may be hidden and timely revealed - 'Double Point Monday' - half off installments on Tuesday, '5% Off Gas' on Wednesday.
  • medical information e.g., reduced flashing for epileptic card holders
  • the card or other device may message a cardholder based on the cardholder's loyalty programs (issue related or otherwise. For example, the card or other device may inform the cardholder when points are earned for a purchase and when points are not earned. According to some example embodiments, different light shows may be provided for different accounts (e.g., debit and credit).
  • a glow card or other device may be a cheaper, light-brilliant alternative to other types of cards (e.g., metal) while also providing a cardholder information either through text, imagery, colors, movement speed or flashing of a displayed object, and or the like.
  • the device may include a static or dynamic stripe, traditional stripe tracks, JIS 1 and/or JIS 2, and/or the like.
  • a metal card or other device may be improved, for example, with precious metals and mirror finishes.
  • metal may be deposited using vapor deposition (e.g., CVD, PCVD, EPCVD, PVD) using, for example, a vacuum chamber at, for example, class 100,000, 1000, 100 or 1.
  • the deposition may be conformal and/or result in a planar surface.
  • a card may have different thicknesses in different areas (e.g., battery area may be thicker) and the deposition may result in a planar or approximately planar surface.
  • a mask may be provided, for example, by using resist based processes and/or stickers.
  • a sticker may be applied to a layer on which metal will be deposited and removed after the deposition.
  • a skin material may be thick (e.g., thicker than conventional skin layers) and made of, for example a flexible glass or other material that withstands elevated temperature processing (e.g., high temperature and/or pressure depositions) and protects internal components.
  • the skin material may be the same on both sides of a card or different.
  • a clear or colored plastic layer may be applied.
  • a clear protective layer may be applied for printing.
  • the card or other device may be weighted to provide the experience of, for example, a full metal card where metal is deposited on a non-metal skin and a non-metal finish is applied.
  • the corners or edges of a card may be coated such that when struck against an object emulates the sound of, for example, a full metal card.
  • a grinding and/or other polishing may be applied, for example, when applying different precious metals (e.g., gold over silver, or silver over gold) or when printing three dimensional images.
  • precious metals e.g., gold over silver, or silver over gold
  • a skin layer or other layer may be etched with a pattern prior to metal deposition to provide an inlay.
  • a skin layer or other layer e.g., a plastic layer
  • a mask e.g., sticker
  • mechanical engraving may be performed.
  • a device may include a first contact chip with a first primary account number (PAN) in storage, the first PAN associated with a first payment method, and a second contact chip with a second PAN in storage, the second PAN associated with a second payment method.
  • the first payment method of the device may be credit
  • the second payment method of the device may be equated monthly installments (EMI).
  • Payment cards are provided that may be powered interactive payment cards or static payment cards. Interactive cards may have, for example, any number of buttons and/or displays to receive manual input from cardholders and/or display information to cardholders.
  • Batteries may be included in interactive cards to power electronics such as displays and other electrical components in order to provide advanced functionality even when, for example, a card is not under power of an external device (e.g., a point-of- sale terminal).
  • Non-powered and/or non-interactive cards may be provided with advanced capabilities through, for example, the inclusion of advanced payment applets that can trigger different functionalities in different situations. In doing so, the payment application can receive data from a transaction and initiate different capabilities in the same manner than a cardholder can initiate different capabilities.
  • Advanced transaction processing capabilities at the terminal, merchant, merchant processor, payment network, bank, bank processor, or other device may receive data from and/or provide data to payment applets located on powered, non-powered, manually interfacing, and/or non-manually interfacing cards.
  • a payments applet may be provided, for example, in a processing chip such as a secure processing chip that includes a secure element such as a secure memory element.
  • a processing chip may communicate with a point-of-sale terminal through any number of interfaces such as a contact interface (e.g., contact EMV), a contactless interface (e.g., an RFID antenna, a magnetic communications device, or any type of interface (e.g., a dynamic and/or static QR code or other type of barcode provided through a display).
  • a contact interface e.g., contact EMV
  • a contactless interface e.g., an RFID antenna
  • a magnetic communications device e.g., a magnetic communications device
  • any type of interface e.g., a dynamic and/or static QR code or other type of barcode provided through a display.
  • a processor may be coupled to other chips (e.g., processors) that provide different interfaces.
  • a contactless chip may provide a contactless interface and a contact chip may provide a contact interface.
  • a payment applet may be provided in a contact chip and may include contact chip features and a payment applet may be provided in a contactless chip and may include contactless chip features.
  • Additional software e.g., firmware
  • a single chip may have an applet that includes multiple interface features such as contact chip features and contactless chip features.
  • interfaces may have different performance and protocols that take advantage of the capabilities of the differentiating interfaces. For example, a applet may have a faster contactless protocol than a contact applet and, as such, may have the capability of completing a contactless transaction faster than the applet may complete a contact transaction (or vise versa) in certain scenarios.
  • Applets may include one or more applications and such applications may be prioritized such that a point-of-sale reader may initiate applications that are applicable to that point-of-sale reader in such a prioritization.
  • a card or other device may change the priority of such applications based on input, for example, on the device (e.g., a manual input on a manual input interface such as a button on a battery powered card).
  • the applet may change priorities alternatively, for example, based on pre-determined prioritizations based on data that is learned by the applet during one or more than one transaction.
  • payment applets may store in a secure element or other structure some or all data that is introduced to a payment applet after a payment applet is utilized to make a purchase transaction.
  • the applet may utilize the received data to make determinations that may change the operation of the applet temporarily, permanently, and/or conditionally.
  • a payment applet may receive data associated with the country that the card was utilized in for a transaction.
  • the payment applet may reset a transaction and utilize the information in the subsequent approved transaction or, for example, the applet may permit the transaction to complete and utilize the information in the subsequent transaction.
  • a card may have different payment card numbers associated with different countries and each payment card number may carry different economics (e.g., interchange and/or assessment fees) based on the country where the card number is utilized.
  • a device may change the payment card number based on the country where the card is located in order to provide improved economics (e.g., interchange and/or assessment fees).
  • the device may, for example, change a default parameter (e.g., payment account number) based on one transaction or receiving the same data (e.g., same country) for a number of transactions (e.g., for 2, 3, 4, 5, or more than 5 transactions).
  • a default parameter e.g., payment account number
  • a number of transactions e.g., for 2, 3, 4, 5, or more than 5 transactions.
  • an applet may receive manual input (e.g., from a button on the device or information associated with a button press on an external device such as a mobile phone) that may cause the applet to initiate an application or prioritize an application associated with a particular account (e.g., a personal account) of a particular payment product (e.g., a credit card) of a particular network (e.g., Mastercard, Visa, Mastercard, JCB, UPI, etc.).
  • a particular account e.g., a personal account
  • a particular payment product e.g., a credit card
  • a particular network e.g., Mastercard, Visa, Mastercard, JCB, UPI, etc.
  • a cardholder may on the device that includes the applet (e.g., a powered card) or another device (e.g., a mobile phone associated with the cardholder) select a payment network, payment product, payment account, and/or payment option and provide information associated with this selection to the applet. This may be done via a direct electrical coupling on the device between the button and the applet. Alternatively, for example, this may be done remotely during a transaction by providing data to the applet associated with the selection (e.g., during contact EMV scripting and/or during contactless EMV scripting).
  • a device e.g., a telephonic payment device or card
  • the devices may be utilized, for example, to make a contact or contactless transaction.
  • An applet on the device may be utilized to manage the transaction flow between the device and the point of sale terminal.
  • the device may manage the transaction for a first payment card account (e.g., a debit account) and that first payment card account may be associated with the country of payment account issuance (e.g., the United States).
  • the applet may learn that the transaction is occurring in the United States from data received from the point of sale device during the payment transaction.
  • the applet may be structured to recognize the country and perform different activities based on the recognized country. For example, if the country recognized matches the country of issuance then the applet may ensure that a transaction only completes if the payment account for the transaction matches the payment account the applet recognizes is to be utilized for the recognized country. Thus, an applet may be set so that a particular account (e.g., debit) it utilized when the device is in the country of issuance and that a different account (e.g., a pre-paid account such as a foreign exchange pre-paid account) is utilized when the device is not in the country of issuance. If the recognized country matches the payment card account desired for that country then the apple may permit the transaction to complete.
  • a particular account e.g., debit
  • a different account e.g., a pre-paid account such as a foreign exchange pre-paid account
  • the payment applet may attempt to change the account of the transaction or may terminate the transaction without the transaction successfully completing. This may be done, for example, by the card not proving a confirmation or acknowledgement of a transaction approval.
  • a device may include numerous steps of bi- directional communication to a point-of-sale device and the point-of-sale-device may include multiple steps of communication data bi-directionally to the merchant bank, payment network, issuer, issuing bank processor, and/or a variety of additional processing or other elements.
  • the payment applet may then attempt to re-initiate a transaction with the payment account for the previously recognized country.
  • the payment applet may change the account utilized in a payment transaction in order to, for example, increase the chance that the applet does not have to restart by assuming, for example, that at least a number of subsequent transactions will occur in the same country as the previously detected country.
  • a payment applet may not be able to restart a transaction and that the device holder may have to dis-engage the device from the point-of-sale reader and re-engage with the point-of-sale reader.
  • a cardholder may have to remove a card from an EMV terminal the first time a cardholder enters a country and reinsert the card into the EMV terminal each time a cardholder enters a country.
  • a card may wait for a number of transactions (e.g., 2 transactions) that are associated with an account change before making the account change for future transactions.
  • a number of transactions e.g. 2 transactions
  • that cardholder may, if the payment applet cannot re-initiate a transaction itself, find themselves dis-engaging from a reader on two consecutive occasions if the device is set to change the account used initially for a transaction only after two changes are detected.
  • a card may include program logic for predicting situations and pre-emptively changing accounts (or other features) based on those predictions.
  • a payment applet on a device (e.g., a card or a mobile telephonic device) for different countries, groups of countries, country of issuance, countries outside the country of issuance, etc. Accordingly, for example, a payment device may change to a U.S. payment card when in the U.S, a French payment when in France, a German payment card when in Germany, and may default to an international foreign exchange card (e.g., a foreign exchange pre-paid card) if the device does not have a territory-specific account for a particular country or territory.
  • a device e.g., a card or a mobile telephonic device
  • a payment device may change to a U.S. payment card when in the U.S, a French payment when in France, a German payment card when in Germany, and may default to an international foreign exchange card (e.g., a foreign exchange pre-paid card) if the device does not have a territory-specific account for a particular country or territory.
  • External information may be sent to a payment applet during a transaction in order to update the payment applet.
  • a mobile telephonic device may determine the location of the mobile telephonic device and may communicate information to a remote server.
  • the remote server may be reviewed by a processing system, for example, to see if any updates occurred during a payment transaction with a device and updates may be provided to the payment applet of the device undergoing the payment transaction during a payment transaction.
  • the country may be updated by an external device.
  • Any type of information may be downloaded such as, for example, any setting or updated to program logic.
  • the payment device may have its own wireless connection (e.g., cellular connection, Bluetooth connection, etc.) and may receive updates from this connection before, during, and/or after a payment transaction.
  • a payment device may communicate with an external non-point of sale device directly (e.g., a card may communicate with a mobile phone via a Bluetooth or other wireless connection).
  • Non-wireless connections may also be utilized (e.g., a device may have an EMV slot and may electronically couple to a card via that EMV slot).
  • a payment applet may be also made to other communication systems such as, for example, dynamic barcode systems (e.g., dynamic QR systems) as well as dynamic magnetic stripe communications systems.
  • the device may change the account on its magnetic stripe as well as displayed QR payment information in addition to its contact and contactless payment information.
  • an applet may be generally considered, for example, all software/firmware in a device that is utilized to complete a purchase transaction or may be considered individual applets running on individual environments.
  • a device may have an applet that runs on a first operating system to perform a first set of functions (e.g., Visa EMV contactless) and a second applet that runs on a second operating system to perform a second set of functions (e.g., QR code).
  • Intermediary software/firmware as well as intermediary hardware e.g., processor(s) may be utilized to share information and/or controls between applets and/or other hardware and/or software/firmware portions of a device.
  • a payment applet on a device may receive time as part of a transaction process. Accordingly, the device may be utilize the time of a transaction in determining, for example, an account to utilize or a payment option or other metric to utilize. The device may, for example, utilize the time also to update a time tracking device such as a timer/counter. In doing so, for example, the card may be able to determine the time of a transaction before a transaction process starts. Accordingly, for example, a card may be able to predict when the day changes.
  • a first account may be utilized, for example, for a first period of time and a second account may be utilized for a second period of time.
  • a first card account may be utilized for a period of time (e.g., the first 72 hours) and a second card account may be utilized for a second period of time (e.g., after the first 72 hours).
  • additional security may be provided so if a card is compromised in the mail the relevancy of the card compromise may be reduced.
  • a debit or pre-paid card may be the card for the first period of time (e.g., first 5 days) and then the card may be switched over to a different product such as a credit account for a credit product.
  • a card may be instantly issued to a consumer while a credit setup process is being performed that may, for example, determine the credit limit and/or other metrics associated with the credit card.
  • a payment applet may receive the date of a transaction in addition to the time.
  • a device may utilize this date information in the current transaction and/or subsequent transactions.
  • a cardholder e.g., a physical card or a virtual card on a mobile device
  • a cardholder e.g., a physical card or a virtual card on a mobile device
  • a cardholder e.g., a physical card or a virtual card on a mobile device
  • a first account may be utilized on the first half of the moth (e.g., beginning of the month to the end of the 15 th of the month) and a second account may be utilized on the second half of the money (e.g., starting on the 16t of the month to the end of the month).
  • a cardholder may have two different payment dates - one associated with the first account at a firs time and one associated with a second account at a second time.
  • the card may automatically recognize the date during a transaction and terminate the transaction if the account associated with that date is not being utilized so that another transaction may be started with that account utilized by the payment applet.
  • recognized time by the device may be utilized in conjunction with the recognized date and a timing circuit in order to predict when a new period starts so that the appropriate account can be utilized in a point-of-sale terminal when a transaction is made in that period.
  • a cardholder may be provide with material economic value for a card that provides a longer time for a payment to be due by having multiple payment periods.
  • a card may switch between two, three, four, five or more accounts in order to provide a cardholder with two, three, four, five or more, respectively, credit payment periods.
  • the different accounts may have a shared credit line and/or may have different credit lines.
  • the value of a transaction may be utilized, for example, as a switching mechanism in a payment applet to switch between accounts, options, and or other payment features.
  • a transaction associated with an amount larger than a particular amount e.g., $100, $500, or $1000
  • a first account e.g., a debit account
  • a second account e.g., a credit account
  • a payment applet may alternatively, for example, switch a transaction from a first option (e.g., a credit option on a credit account) to a second option (e.g., an installment option on a credit account.
  • a payment applet may determine to embed payment option data (e.g., installment data) in to payment information in a particular scenario or set of scenarios.
  • This payment information may then be communicated through a payment network to an issuing bank's processor.
  • An issuing bank's processor may authorize the transaction.
  • the payment option data may be extracted (e.g., from a copy of the authorization message) and may be utilize do initiate an additional transaction such as a statement credit/offset (e.g., for a pay with points) or a statement credit/offset with monthly equated statement charges and/or additional monthly fees over a number of months (e.g., for an equated monthly installment over those number of months).
  • a statement offset may be provided, for example, via a monetary file transfer between two different accounts.
  • One account for example, may be an escrow and another account may be the account associated with the payment device for the transaction. Accordingly, a $60 credit transaction may be offset by a $60 transfer.
  • the description of the offset transaction may be, for example, associated with the feature.
  • the description may state "Toys R Us 6/26 for $60 offset with 6 month EMI" and then each month a $10 installment may be applied with the description "Toys R Us 6/26 Installment X of 6" where X is the month installment of the 6 months of installments.
  • a fee may be added (e.g., a percentage or fixed fee) to the aforementioned amount (e.g.. $2 to make the installment $12) or a second line statement may be provided in the statement for the fee (e.g., a second statement line of $2).
  • Payment options may also be selected by a manual interface on a device or a manual interface on a remote device that is then communicated to the transacting device (e.g., via a wireless communication or through transaction data delivered to the transacting device from the point-of- sale terminal).
  • a payment applet may combine data from multiple transactions and utilize this combined data to make determinations on accounts, options, applications, or other attributes to utilize in a payment transaction.
  • Cumulative data such as cumulative transaction amounts may be utilized to determine the amount spent on the payment device over, for example, a period of time, for example, on a particular type of payment (e.g., payment transactions with bi-directional data flow). Accordingly, for example, an account (e.g., a debit account) may be utilized until a particular amount of transaction volume occurs (e.g., $1,000) during a period of time (e.g., each month) and a second account (e.g., a credit aaccount) may be utilized after that until the end of the month.
  • a particular amount of transaction volume e.g., $1,000
  • a second account e.g., a credit aaccount
  • a payment device e.g., a static, non-interactive card
  • a payment device may be able to change accounts and/or payment options based on pre-determined conditions.
  • information may be sent to a device to, for example, update pre-determined conditions to other conditions (e.g., change the cumulative amount to cause a change in an account and/or option to a different cumulative amount as well as the account and/or option changed).
  • updates to one or more payment applets or other software/firmware parts of a device may be updated during a transaction (e.g., through transaction information0 or at any time (e.g., through a wireless communication by a wireless communication communications device on the device).
  • a device may utilize (e.g., via a payment applet) an approval and/or a cumulative number of approvals and/or additional transaction data to initiate a feature.
  • a pre-stored message may be displayed on a display (e.g., an bi-stable display, non bi-stable display, and/or a display of individual light emitting diodes LEDs or other sources of light) for a particular transaction approval (e.g., first transaction) particular group of transaction approvals (e.g., first 10 transactions) and/or all transactions approvals of a particular type (e.g., first transaction approval after a new year).
  • a welcome message may be provided to a cardholder for the first one, two, or more than two transaction approvals.
  • the number of transaction approvals may also be utilized, for example, to provide a game of chance and/or a sweepstakes.
  • a prize may be randomly hidden in each payment account (e.g., a prize of a free transaction or a discount on a transaction) and a message may be displayed to a cardholder indicative of whether or not a transaction approval was a winning transaction approval and the prize associated with that winning approval.
  • prizes may be distributed over a number of cards randomly such that, for example, multiple prizes may be provided on some cards and no prizes may be provide on other cards.
  • a mobile device may have a mobile wallet with a virtual card that corresponds to a physical card.
  • a cardholder may select different accounts and/or options on the virtual card. This selection information may be stored on, for example, a remote server and delivered to a transacting device (e.g., a static, non- interactive card) during a transaction.
  • a payment applet on the static-non-interactive card may determine whether or not to terminate a payment transaction based on the received information and change the account and/or option as desired by the cardholder and re- initiate the transaction.
  • physical payment cards may be loaded as virtual cards into a virtual wallet of a mobile device (e.g., a mobile telephonic device).
  • a user may, for example, browse different virtual cards in the virtual wallet and utilize those cards for online transactions (e.g., by reading a displayed card number) and/or an in-store transaction (e.g., by initiating a contactless transaction between the mobile telephonic device and a contactless point-of-sale terminal).
  • cards with interactive buttons and cards without interactive buttons may either or both be loaded into virtual wallets and receive virtual buttons to perform additional functionalities (e.g., the same functionalities on physical buttons of physical interactive cards).
  • a mobile wallet may be provided in which some virtual cards (e.g., those that correspond to physical interactive cards), some virtual cards (e.g., cards associated with a particular network, and/or virtual cards of a particular type (e.g., all credit cards) and/or all virtual cards may be provided with interactive features when they are digitized and uploaded into a virtual wallet.
  • some virtual cards e.g., those that correspond to physical interactive cards
  • some virtual cards e.g., cards associated with a particular network, and/or virtual cards of a particular type (e.g., all credit cards) and/or all virtual cards
  • a virtual wallet may be provided on a website and retrieved after a user logs into the website and identified themselves and is completing a purchase transaction.
  • a virtual wallet may alternatively be provided on a device such as, for example, a watch, phone, or a card.
  • Such devices may have wireless communication capabilities (e.g., cellular capabilities) to communicate data (e.g., virtual card data).
  • data e.g., virtual card data
  • a non-interactive card with no buttons may be loaded into a wallet and the virtual card may have a virtual button associated with point redemption and one or more virtual buttons associated with one or more installment options (e.g., 6-month, 12-month, 18-month, and/or 24-mont installments).
  • the virtual card may have a virtual button for one or more accounts (e.g., one or more debit, credit, and/or pre-paid accounts).
  • an interactive card with one or more payment account buttons may be loaded into one or more virtual wallets as a virtual card that has one, more than one, or all of the buttons of the physical card as virtual buttons on the virtual card.
  • an issuing bank may provide a virtual wallet where any card from that bank may be loaded into the virtual wallet and virtual buttons may be added to all of the cards for additional features not present on the physical cards (e.g., unless the physical cards are interactive cards). Additional features may be added as virtual buttons to all or some of an issuing bank's virtual cards after the card has been digitized/virtualized and put in the virtual wallet. Accordingly, for example, the functionality of a virtual card may be updated as new features are deployed.
  • FIG. 1 is an illustration of a card and architecture constructed in accordance with the principles of the present invention
  • FIG. 2 is an illustration of a device constructed in accordance with the principles of the present invention.
  • FIG. 3 is an illustration of a network topology constructed in accordance with the principles of the present invention.
  • FIG. 4 is an illustration of a device constructed in accordance with the principles of the present invention.
  • FIG. 5 is an illustration of a device constructed in accordance with the principles of the present invention.
  • FIG. 6 is an illustration of a process flow chart constructed in accordance with the principles of the present invention.
  • FIG. 7 is an illustration of a device constructed in accordance with the principles of the present invention.
  • FIG. 8 is an illustration of a device constructed in accordance with the principles of the present invention.
  • FIG. 9 is an illustration of a process flow chart constructed in accordance with the principles of the present invention.
  • FIG. 10 is an illustration of a process flow chart constructed in accordance with the principles of the present invention.
  • FIG. 11 is an illustration of a process flow charts constructed in accordance with the principles of the present invention.
  • FIG. 12 is an illustration of a process flow chart constructed in accordance with the principles of the present invention.
  • FIG. 13 is an illustration of a process flow chart constructed in accordance with the principles of the present invention.
  • FIG. 14 is an illustration of a process flow chart constructed in accordance with the principles of the present invention.
  • FIG. 15 is an illustration of a thin mechanical slider usable on a card and/or card chip in accordance with the principles of the present invention.
  • FIG. 16 is an illustration of features constructed in accordance with the principles of the present invention.
  • FIG. 17 is an illustration of features constructed in accordance with the principles of the present invention.
  • FIG. 18 is an illustration of features constructed in accordance with the principles of the present invention.
  • FIG. 19 is an illustration of features constructed in accordance with the principles of the present invention.
  • FIG. 20 is an illustration of features constructed in accordance with the principles of the present invention.
  • FIG. 21 is an illustration of features constructed in accordance with the principles of the present invention.
  • FIG. 22 is an illustration of features constructed in accordance with the principles of the present invention.
  • FIG. 23 is an illustration of features constructed in accordance with the principles of the present invention.
  • FIG. 24 is an illustration of features constructed in accordance with the principles of the present invention.
  • FIG. 25 is an illustration of features constructed in accordance with the principles of the present invention.
  • FIG. 26 is an illustration of features constructed in accordance with the principles of the present invention.
  • FIG. 27 is an illustration of features constructed in accordance with the principles of the present invention.
  • FIG. 28 is an illustration of features constructed in accordance with the principles of the present invention.
  • FIG. 29 is an illustration of features constructed in accordance with the principles of the present invention.
  • FIG. 30 is an illustration of features constructed in accordance with the principles of the present invention.
  • FIG. 31 is an illustration of features constructed in accordance with the principles of the present invention.
  • FIG. 32 is an illustration of features constructed in accordance with the principles of the present invention.
  • FIG. 33 is an illustration of a card and architecture constructed in accordance with the principles of the present invention.
  • FIG. 34 is an illustration of a device constructed in accordance with the principles of the present invention.
  • FIG. 35 is an illustration of a network topology constructed in accordance with the principles of the present invention.
  • FIG. 36 is an illustration of a device constructed in accordance with the principles of the present invention.
  • FIG. 37 is an illustration of a device constructed in accordance with the principles of the present invention.
  • FIG. 38 is an illustration of a process flow chart constructed in accordance with the principles of the present invention.
  • FIG. 39 is an illustration of a device constructed in accordance with the principles of the present invention.
  • FIG. 40 is an illustration of a device constructed in accordance with the principles of the present invention.
  • FIG. 41 is an illustration of a process flow chart constructed in accordance with the principles of the present invention.
  • FIG. 42 is an illustration of a process flow chart constructed in accordance with the principles of the present invention.
  • FIG. 43 is an illustration of a process flow charts constructed in accordance with the principles of the present invention.
  • FIG. 44 is an illustration of a process flow chart constructed in accordance with the principles of the present invention.
  • FIG. 45 is an illustration of a process flow chart constructed in accordance with the principles of the present invention.
  • FIG. 46 is an illustration of a process flow chart constructed in accordance with the principles of the present invention.
  • FIG. 47 is an illustration of a thin mechanical slider usable on a card and/or card chip in accordance with the principles of the present invention.
  • FIG. 48 is an illustration of hardware in a loyalty hosting system
  • FIG. 49 is an illustration of cards and architectures in accordance with the principles of the present invention.
  • FIG. 50 is an illustration of cards in accordance with the principles of the present invention.
  • FIG. 51 is an illustration of cards in accordance with the principles of the present invention.
  • FIG. 52 is an illustration of card displays in accordance with the principles of the present invention.
  • FIG. 53 is an illustration of cards in accordance with the principles of the present invention.
  • FIG. 54 is an illustration of dynamics magnetic stripes in accordance with the principles of the present invention.
  • FIG. 55 is an illustration of dynamics magnetic stripes in accordance with the principles of the present invention.
  • FIG. 56 is an illustration of devices in accordance with the principles of the present invention.
  • FIG. 57 is an illustration of network topologies in accordance with the principles of the present invention.
  • FIG. 58 is an illustration of mobile devices in accordance with the principles of the present invention.
  • FIG. 59 is an illustration of cards in accordance with the principles of the present invention.
  • FIG. 60 is an illustration of cards in accordance with the principles of the present invention.
  • FIG. 61 is an illustration of cards in accordance with the principles of the present invention.
  • FIG. 62 is an illustration of cards in accordance with the principles of the present invention.
  • FIG. 63 is an illustration of cards in accordance with the principles of the present invention.
  • FIG. 64 is an illustration of cards in accordance with the principles of the present invention.
  • FIG. 65 is an illustration of systems in accordance with the principles of the present invention.
  • FIG. 66 is an illustration of systems in accordance with the principles of the present invention.
  • FIG. 67 is a flow diagram illustrating communication sequences in accordance with the principles of the present invention.
  • FIG. 68 is an illustration of cards in accordance with the principles of the present invention.
  • FIG. 69 is an illustration of cards in accordance with the principles of the present invention.
  • FIG. 70 is an illustration of cards in accordance with the principles of the present invention.
  • FIG. 71 is an illustration of a card constructed in accordance with the principles of the present invention.
  • FIG. 72 is an illustration of a card constructed in accordance with the principles of the present invention.
  • FIG. 73 is an illustration of circuitry, and associated waveforms, constructed in accordance with the principles of the present invention.
  • FIG. 74 is an illustration of a card constructed in accordance with the principles of the present invention.
  • FIG. 75 is an illustration of a card constructed in accordance with the principles of the present invention.
  • FIG. 76 is an illustration of a card constructed in accordance with the principles of the present invention.
  • FIG. 77 is an illustration of process flow charts constructed in accordance with the principles of the present invention.
  • FIG. 78 is an illustration of a card constructed in accordance with the principles of the present invention.
  • FIG. 79 is an illustration of a card constructed in accordance with the principles of the present invention.
  • FIG. 80 is an illustration of a card constructed in accordance with the principles of the present invention.
  • FIG. 81 shows cards and architectures constructed in accordance with the principles of the present invention.
  • FIG. 82 shows devices constructed in accordance with the principles of the present invention.
  • FIG. 83 shows network topologies arranged in accordance with the principles of the present invention.
  • FIG. 84 shows transaction verification methods according to principles of the present invention.
  • FIG. 85 shows cards according to principles of the present invention.
  • FIG. 86 shows a card according to principles of the present invention
  • FIG. 87 shows a token transaction method performed in accordance with the principles of the present invention
  • FIG. 88 shows a card according to principles of the present invention
  • FIG. 89 shows a card according to principles of the present invention.
  • FIG. 90 shows a card according to principles of the present invention
  • FIG. 91 shows a card according to principles of the present invention
  • FIG. 92 shows a mobile telephonic device according to principles of the present invention.
  • FIG. 93 shows a card with vertical print differentiation according to principles of the present invention.
  • FIG. 94 shows a card according to principles of the present invention.
  • FIG. 95 shows a card according to principles of the present invention.
  • FIG. 96 shows a card according to principles of the present invention.
  • FIG. 97 shows a GUI of a device according to principles of the present invention.
  • FIG. 98 is an illustration of a card and architecture constructed in accordance with the principles of the present invention.
  • FIG. 99 is an illustration of a device constructed in accordance with the principles of the present invention.
  • FIG. 100 is an illustration of a network topology constructed in accordance with the principles of the present invention.
  • FIG. 101 is an illustration of a device constructed in accordance with the principles of the present invention.
  • FIG. 102 is an illustration of a device constructed in accordance with the principles of the present invention.
  • FIG. 103 is an illustration of a device constructed in accordance with the principles of the present invention.
  • FIG. 104 is an illustration of flow charts constructed in accordance with the principles of the present invention.
  • FIG. 105 is an illustration of a device constructed in accordance with the principles of the present invention.
  • FIG. 106 is an illustration of a device constructed in accordance with the principles of the present invention.
  • FIG. 107 is an illustration of a device constructed in accordance with the principles of the present invention.
  • FIG. 108 is an illustration of a device constructed in accordance with the principles of the present invention.
  • FIG. 1 shows card 100 that may include, for example, dynamic magnetic stripe communications device 101, one or more displays (e.g., displays 112, 113 and 125), permanent information 120, light sensor 127, one or more buttons (e.g., buttons 130-134, 198 and 199), lights 135-138, 196 and 197, and dynamic number 114 which may include a permanent portion 111.
  • Permanent portion 111 may be, for example, printed, embossed and/or laser etched on card 100.
  • Display 112 may display a dynamic number entirely, and/or partially.
  • Display 113 may be utilized to display a dynamic code (e.g., a dynamic security code).
  • Display 125 may display logos, barcodes, and/or one or more lines of information (e.g., may display a coupon code).
  • a display e.g., at least one of displays 112, 113 and 125
  • a bi-stable display may be a display that maintains an image without power.
  • Card 100 may include permanent information 120 including, for example, information specific to a user (e.g., a user's name and/or username) and/or information specific to a card (e.g., a card issue date and/or a card expiration date).
  • information specific to a user e.g., a user's name and/or username
  • information specific to a card e.g., a card issue date and/or a card expiration date.
  • Card 100 may include a dynamic magnetic communications device.
  • a dynamic magnetic communications device may take the form of a magnetic encoder and/or a magnetic emulator.
  • a magnetic encoder may change the information located on a magnetic medium such that a magnetic stripe reader may read changed magnetic information from the magnetic medium.
  • a magnetic emulator may generate electromagnetic fields that directly communicate data to a magnetic stripe reader. Such a magnetic emulator may communicate data serially to a read-head of the magnetic stripe reader.
  • Card 100 may include one or more buttons, for example, buttons 130-134, 198 and 199. Buttons 130-134, 198 and 199 may be, for example, mechanical buttons, capacitive buttons, light sensors and/or a combination thereof.
  • Button 199 may be used, for example, to communicate information through dynamic magnetic stripe communications device 101 indicative of a user's desire to communicate a single track of magnetic stripe information.
  • a button e.g., button 199
  • pressing a button may cause information to be communicated through device 101 when an associated read-head detector detects the presence of a read-head of a magnetic stripe reader and/or at a specific frequency.
  • Button 198 may be utilized to communicate (e.g., after button 198 is pressed and after a read-head detects a read-head of a reader) information indicative of a user selection (e.g., to communicate two tracks of magnetic stripe data).
  • Multiple buttons may be provided on a card and each button may be associated with a different user selection.
  • buttons 198 and button 199 may each be associated with, for example, a different third party service provider feature (e.g., an application facilitating a coupon) and may be changed by a user at any time.
  • a different third party service provider feature e.g., an application facilitating a coupon
  • a user may select a third party feature from a list displayed to the user. For example, the user may scroll through a list of features on a display (e.g., display 125). A user may scroll through a list using buttons on a card (e.g., buttons 130-134). The list of features may be displayed to the user individually, in groups and/or all features may be simultaneously displayed.
  • a display e.g., display 125
  • buttons on a card e.g., buttons 130-134.
  • the list of features may be displayed to the user individually, in groups and/or all features may be simultaneously displayed.
  • a third party feature associated with a button may be changed by a user, for example, on a graphical user interface (GUI) provided by a device provider, ecosystem provider, application manager provider, remote facility provider, card issuer, processor, and/or any other entity (which may be the same or different entities).
  • GUI graphical user interface
  • an ecosystem provider may, on its website and/or via an application, allow a user to change the third party feature performed when the third party's feature button is selected by a user on the user's card or other device.
  • a third party service provider may provide a reward (e.g., a coupon) from a collection of rewards based on, for example, one or more card transactions.
  • the fact the user has received the reward may be presented on a profile page of the user.
  • a user's profile may be updated to state that the user has earned a reward and the user may receive the reward (e.g., via email).
  • a user may be provided with a GUI, for example, a GUI on a mobile telephonic device of the user, when the user makes a purchase, to identify and/or use the reward earned by the user.
  • the selection of a feature may or may not have a cost associated with it. If a cost is associated with the feature, for example, the cost may be added to a customer's statement (e.g., added to a credit or debit purchase) for a particular transaction. A fixed-fee or variable-fee (e.g., a percentage of the transaction) may then be removed from the fee charged to the user and distributed among particular parties (e.g., distributed to the card issuer, application manager provider, ecosystem provider, device provider and/or other entity). The remainder of the fee, if any, may be provided, for example, to the third party service provider.
  • a cost may be added to a customer's statement (e.g., added to a credit or debit purchase) for a particular transaction.
  • a fixed-fee or variable-fee e.g., a percentage of the transaction
  • parties e.g., distributed to the card issuer, application manager provider, ecosystem provider, device provider and/or other entity.
  • a cost may be associated to a feature selection, but may not be a cost to a user.
  • the cost may be a cost to a third party service provider (e.g., an incentive).
  • the cost may be a cost to other entities, for example, the device provider, card issuer, card processor (which may be the same, for example, as the card issuer), and/or any other entity (e.g., card network).
  • a user may select a type of payment on card 100 via manual input interfaces (e.g., buttons 130-134).
  • the manual input interfaces may correspond to displayed options (e.g., displayed on display 125).
  • Selected information may be communicated to a magnetic stripe reader via a dynamic magnetic stripe communications device.
  • Selected information may also be communicated to a device (e.g., a mobile telephonic device) including a capacitive sensor and/or other type of touch sensitive sensor.
  • Lights 135-138, 196 and 197 may be associated with buttons 131-134, 198 and 199. Each of lights 135-138, 196 and 197 may indicate, for example, when a button is pressed. In a case where a button may activate card 100 for communications, a light may begin blinking to indicate card 100 is still active (e.g., for a period of time) while reducing power expenditure. Although not shown, a light may be provided for button 130.
  • Card 100 may include light sensor 127. Light sensor 127 may, for example, receive information from a light source (e.g., a display of a mobile telephonic device and/or a laptop computer).
  • a light source e.g., a display of a mobile telephonic device and/or a laptop computer.
  • Card 100 may include, for example, any number of light sensors 127.
  • Light sensor 127 may be utilized such that a display screen, or other light emitting device, may communicate information to light sensors 127 via light.
  • Display 125 may allow a user to select (e.g., via buttons) options on display 125 that instruct the card to communicate (e.g., via a dynamic magnetic stripe communications device, RFID and/or exposed IC chip) to use a debit account, credit account, pre-paid account, and/or point account for a payment transaction.
  • Architecture 150 may be utilized with any card (e.g., any card 100).
  • Architecture 150 may include, for example, processor 120, display 140, driving circuitry 141, memory 142, battery 143, radio frequency identification (RFID) 151, integrated circuit (IC) chip 152, electromagnetic field generators 170, 180, and 185, and read-head detectors 171 and 172.
  • RFID radio frequency identification
  • IC integrated circuit
  • Processor 120 may be any type of processing device, for example, a central processing unit (CPU) and/or a digital signal processor (DSP). Processor 120 may be, for example, an application specific integrated circuit (ASIC). Processor 120 may include on-board memory for storing information (e.g., triggering code). Any number of components may communicate to processor 120 and/or receive communications from processor 120. For example, one or more displays (e.g., display 140) may be coupled to processor 120. Persons skilled in the art will appreciate that components may be placed between particular components and processor 120. For example, a display driver circuit may be coupled between display 140 and processor 120.
  • a display driver circuit may be coupled between display 140 and processor 120.
  • Memory 142 may be coupled to processor 120.
  • Memory 142 may store data, for example, data that is unique to a particular card.
  • Memory 142 may store any type of data.
  • memory 142 may store discretionary data codes associated with buttons of a card (e.g., card 100 of FIG. 1).
  • Discretionary data codes may be recognized by remote servers to effect particular actions.
  • a discretionary data code may be stored in memory 142 and may be used to cause a third party service feature to be performed by a remote server (e.g., a remote server coupled to a third party service such as a coupon provider).
  • Memory 142 may store firmware that, for example, controls triggering and/or the like.
  • Architecture 150 may include any number of reader communication devices.
  • architecture 150 may include at least one of IC chip 152, RFID 151 and a magnetic stripe communications device.
  • IC chip 152 may be used to communicate information to an IC chip reader (not illustrated).
  • IC chip 152 may be, for example, an EMV chip.
  • RFID 151 may be used to communicate information to an RFID reader.
  • RFID 151 may be, for example, an RFID tag.
  • a magnetic stripe communications device may be included to communicate information to a magnetic stripe reader.
  • a magnetic stripe communications device may provide electromagnetic signals to a magnetic stripe reader.
  • Electromagnetic field generators 170, 180, and 185 may include a coil (e.g., each may include a coil) wrapped around one or more materials (e.g., a soft-magnetic material and a non- magnetic material).
  • Each electromagnetic field generator may communicate information, for example, serially to a receiver of a magnetic stripe reader for a particular magnetic stripe track.
  • a single coil may communicate multiple tracks of data.
  • Architecture 150 may include read head detectors 171 and 172.
  • Read-head detectors 171 and 172 may be configured to sense the presence of a magnetic stripe reader (e.g., a read-head housing of a magnetic stripe reader). Information sensed by the read-head detectors 171 and 172 may be communicated to processor 120 to cause processor 120 to communicate information serially from electromagnetic generators 170, 180, and 185 to magnetic stripe track receivers in a read-head housing of a magnetic stripe reader.
  • a magnetic stripe communications device may change the information communicated to a magnetic stripe reader at any time.
  • Processor 120 may, for example, communicate user-specific and card-specific information through RFID 151, IC chip 152, and/or electromagnetic generators 170, 180, and 185 to card readers coupled to remote information processing servers (e.g., purchase authorization servers).
  • Driving circuitry 141 may be utilized by processor 120, for example, to control electromagnetic generators 170, 180 and 185.
  • Architecture 150 may include, for example, a light sensor. Architecture 150 may receive information from a light sensor. Processor 120 may determine information received by a light sensor.
  • FIG. 2 shows device 200 that may be, for example, a mobile telephonic device and/or other device (e.g., portable computer such as a portable tablet computer).
  • Device 200 may include, for example, housing 202, display 210, device card 220, virtual buttons 230, 231 and 240, virtual lights 242-247, dynamic card number and verification code 245, and identification information 250.
  • Display 210 may include, for example, light- sensitive and/or touch-sensitive elements.
  • Device 200 may communicate information to a card reader, for example, via a contactless signal (e.g., an RFID signal) and/or a contact-based signal (e.g., a USB connection).
  • a contactless signal e.g., an RFID signal
  • a contact-based signal e.g., a USB connection
  • Device 200 may include a device card 220 and/or virtual buttons 230 and 231.
  • Device card 220 may be a virtual representation of a card and/or any information identifying a payment method (e.g., credit account number).
  • a payment method e.g., credit account number
  • any physical card described herein may be provided as a device card on, for example, a computing system (e.g., a mobile telephonic device and/or a computer).
  • Physical buttons of a physical card may, for example, correspond to virtual buttons of a device card.
  • Virtual button 230 may, for example, correspond to one feature (e.g., an opportunity to earn a coupon) from a third party service provider while virtual button 231 may, for example, correspond to another feature (e.g., the opportunity to add value to a coupon) from the same or a different third party service provider.
  • every feature may not be provided by a third party service provider.
  • the device provider may provide features.
  • All features for a card may be utilized with a particular payment account (e.g., a credit account) such that a payment transaction with that payment account is performed if any feature is selected.
  • a payment account e.g., a credit account
  • an additional one or more features may be associated with a different payment account (e.g., a debit account).
  • a selected feature associated with a credit account may be utilized to make a purchase with credit and may perform an additional action associated with that feature.
  • a different selected feature associated with a debit account may be utilized to make a purchase with debit and may perform an additional action associated with that different feature.
  • Device 200 may include virtual lights 242-247.
  • Virtual lights 242-247 may, for example, indicate an active period during which device 200 may communicate with external devices.
  • Virtual lights 242-247 may correspond to, for example, virtual buttons 230, 231 and 240. According to example embodiments, a fewer or greater number of virtual lights are contemplated (e.g., a center button of virtual buttons 240 may virtually light up).
  • FIG. 3 shows network topology 300 that may include, for example, mobile device 302, contactless device 304, cellular network access infrastructure 306, mobile network 310, wireless access point 308, IP network 312, payment network 314, issuer 320, payment server 316, merchant acquirer 317, ecosystem provider 342, merchant terminal 318, transaction card 333, user electronic device 345 and/or application providers 338, 339 and 340.
  • Mobile device 302 may include, for example, a contactless interface that may initiate, sustain, and/or terminate communication channel 326 between contactless device 304 (e.g., a powered card, non-powered card and/or a device) and mobile device 302.
  • contactless device 304 e.g., a powered card, non-powered card and/or a device
  • Contactless device 304 and mobile device 302 may communicate via channel 326 using any number of contactless mediums, which may include for example, visible, audible, capacitive, electromagnetic, magnetic, and/or RF mediums.
  • Mobile device 302 may provide one or more transceivers, receivers and/or transmitters that may communicate with one or more wired networks (e.g., IP network 312 and/or payment network 314) and/or one or more wireless networks (e.g., a mobile network 310).
  • Mobile device 302 may, for example, communicate with a cellular station over a wireless radio interface (e.g., a GSM air interface) that may be used by mobile device 302 to communicate information (e.g., voice and data) to cellular network access infrastructure 306 (e.g., one or more GSM base transceiver stations, base station controllers and mobile switching centers).
  • cellular network access infrastructure 306 may utilize any multiple access architecture, such as for example, a code-division multiple access architecture and/or a time-division multiple access architecture.
  • Mobile device 302 may, for example, communicate with wireless access point 308 over a wireless interface (e.g., a Bluetooth interface or a Wi-Fi interface). Accordingly, for example, mobile device 302 may access one or more wired networks (e.g., IP network 312 and/or payment network 314) and/or one or more wireless networks 310 (e.g., a mobile network) without the need to first gain access to cellular network access infrastructure 306.
  • a wireless interface e.g., a Bluetooth interface or a Wi-Fi interface
  • wireless networks 310 e.g., a mobile network
  • Payment information may be communicated from contactless device 304 to mobile device 302 in support of a transaction (e.g., a financial transaction) being conducted by mobile device 302.
  • a transaction e.g., a financial transaction
  • IP network 312 e.g., the internet
  • Mobile device 302 may, for example, complete a purchase transaction by first obtaining required payment information from contactless device 304 and then communicating such payment information to network entities (e.g., merchant acquirer 317, payment server 316 and/or issuer 320).
  • network entities e.g., merchant acquirer 317, payment server 316 and/or issuer 320.
  • Mobile device 302 may, for example, already contain payment information necessary to complete a purchase transaction. Accordingly, mobile device may not need to obtain payment information from contactless device 304 before completing a purchase transaction.
  • Payment server 316 may, for example, contact issuer 320 via a network (e.g., payment network 314) with payment information received from mobile device 302 for authorization of a purchase. Once authorized, payment transaction information may be recorded onto a receipt that may be delivered to mobile device 302 via any one or more delivery options (e.g., via a short messaging service of mobile network 310 or an email delivery service of IP network 312).
  • a network e.g., payment network 314
  • payment transaction information may be recorded onto a receipt that may be delivered to mobile device 302 via any one or more delivery options (e.g., via a short messaging service of mobile network 310 or an email delivery service of IP network 312).
  • a payment receipt may, for example, be provided to mobile device 302 as a proof-of-purchase object (e.g., a barcode) that may be provided to a display of mobile device 302 and read by other computing equipment (e.g., a barcode scanner) for proof-of-purchase confirmation.
  • a proof-of-purchase object e.g., a barcode
  • other computing equipment e.g., a barcode scanner
  • Transaction card 333 may, for example, communicate information to merchant terminal 318 (e.g., a magnetic stripe reader, an EMV reader, an RFID reader, an NFC reader and/or a swipe reader attached to an electronic device).
  • Merchant terminal 318 may begin transactions (e.g., point-of-sale transactions) and/or complete transactions via merchant acquirer 317 and/or payment network 314. Accordingly, for example, transaction card 333 may communicate payment information to merchant terminal 318 to initiate a financial transaction.
  • Merchant terminal 318 may communicate transaction information, including at least a portion of the payment information, to merchant acquirer 317.
  • Merchant acquirer 317 may authorize the financial transaction and/or communicate with payment server 316.
  • Payment server 316 may, for example, contact issuer 320 via a network (e.g., payment network 314) with transaction information received from merchant acquirer
  • Application providers 338, 339 and 340 may be one or more entities (e.g., one or more servers) providing applications for association in an ecosystem provided by ecosystem provider 342.
  • Each application may provide one or more features to users of a payment method (e.g., users of contactless device 304 and/or transaction card 333).
  • a payment method e.g., users of contactless device 304 and/or transaction card 333.
  • an application may provide a user an opportunity to earn a coupon and/or add value to a coupon in exchange for using the payment method.
  • application provider 338 may provide coupons as part of a loyalty or rewards program, which may be independent of any payment method.
  • Ecosystem provider 342 may be, for example, a server that maintains associations between applications, users and payment methods.
  • Ecosystem provider 342, and application providers 338, 339 and 340 may communicate with different entities using one or more wired networks (e.g., IP network 312 and/or payment network 314) and/or one or more wireless networks 310 (e.g., a mobile network).
  • Application providers 338, 339 and 340 may communicate directly and/or indirectly with different entities.
  • merchant terminal 318 and/or ecosystem provider 342 may communicate directly with application providers 338, 339 and 340 via IP network 312 and/or via a direct connection (e.g., to validate coupons with a coupon server).
  • application providers 338, 339 and 340 may exchange information (e.g., transactional data) indirectly with issuer 320, merchant acquirer 317 and/or payment network 314 via, for example, ecosystem provider 342.
  • a user electronic device may display a GUI.
  • the GUI may be an application manager used to interface with ecosystem provider 342, and application providers 338, 339 and 340, to define user preferences.
  • Defining user preferences may include, for example, configuring associations (e.g., between users, applications and payment methods), features and/or permissions.
  • the GUI displayed on the user electronic device may, for example, display indicia representing applications that provide features.
  • a user may associate one or more of the applications to one or more payment cards and/or payment card buttons (e.g., mobile device 302 and/or transaction card 333)).
  • the GUI displayed on the user electronic device may be used to, for example, interface with one or more of application providers 338, 339 and 340.
  • application providers 338, 339 and 340 For example, using the GUI, a user may select a coupon from among multiple coupons provided by an application hosted by an application provider.
  • a user may use the GUI displayed on the user electronic device to define how payment network 314, ecosystem provider 342, one or more of application providers 338, 339 and 340, and third-party applications hosted by the one or more application providers (or any other application providing entity) interact for transactions conducted by the user.
  • a user may accept an end license user agreement that outlines how data may be shared between entities.
  • a user may define what data may be shared between entities.
  • data e.g., transactional data
  • ecosystem provider 342 may be provided to ecosystem provider 342 by payment network 314, and/or provided to one or more of application providers 338, 339 and 340 by ecosystem provider 342
  • a user may select at least a portion of data provided to ecosystem provider 342 by payment network 314, and select at least a portion of data to be shared with the one or more of application providers 338, 339 and 340.
  • a customer may select (e.g., via one or more button presses on a powered card and/or device card) an application to be associated to the transaction. Based on the selection, one or more additional actions may be taken besides the processing of the transaction by payment network 314. For example, a user may press a button on a powered card (e.g., transaction card 333).
  • a payment message e.g., a magnetic stripe message reflecting the button that was pressed may be communicated to merchant terminal 318.
  • Merchant terminal 318 may communicate a data string including the payment message and transaction information to payment network 314 via merchant acquirer 317.
  • Payment network 314 may receive the data string.
  • the data string may include a directive instructing payment network 314 to share data with ecosystem provider 342.
  • payment network 314 may share data with ecosystem provider 342 upon receiving the data string and recognizing, based on at least a portion of the data string (e.g., an account number), that data is to be shared.
  • Payment network 314 may cause the same or a different data string to be communicated from payment network 314 (e.g., from a processor within payment network 314) to ecosystem provider 342.
  • an issuer and/or a processor of an issuer may receive data and communicate at least a portion of the data and/or different data based on the received data to ecosystem provider 342.
  • a processor of issuer 320 may parse a data string received from merchant terminal 318 (e.g., via payment network 314) that includes a particular BIN number, may convert the data string into a different format and may forward the converted data string to ecosystem provider 342.
  • a processor of issuer 320 may parse a data string received from merchant terminal 318 (e.g., via payment network 314) that includes a particular BIN number, may convert the data string into a different format and may forward the converted data string to ecosystem provider 342.
  • Ecosystem provider 342 may receive the data string and compare user information (e.g., payment account number and/or payment account holder's name) that may be included within the data string to a user database to obtain a customer ID (e.g., a customer token) associated with the user information.
  • user information e.g., payment account number and/or payment account holder's name
  • customer ID e.g., a customer token
  • sensitive information within the data string may be replaced with the customer ID to create a modified data string, and the sensitive information may be stored either locally within ecosystem provider 342 or remotely to ecosystem provider 342.
  • the modified data string may be communicated to a third party application (e.g., one or more of application providers 338, 339 and 340) via, for example, IP Network 312.
  • ecosystem provider 342 may receive the data string.
  • the data string may be populated with information that may be indicative of which button was pressed on the powered card before being presented to merchant terminal 318.
  • ecosystem provider 342 may generate a third-party message with details that may be shared with a third-party application (e.g., one or more of application providers 338, 339 and 340).
  • the generated data string may include the customer ID and may be communicated to a third party application (e.g., one or more of application providers 338, 339 and 340) via, for example, IP Network 312.
  • a user may elect to share certain transaction information with one or more of application providers 338, 339 and 340 each time a certain button is pressed on the user's powered card before presentment to merchant terminal 318 for payment.
  • Such information may include, for example, merchant information (e.g., merchant's address), date/time information of a purchase, an amount of the purchase, a type of the purchase, and any other information (e.g., the customer ID associated with the customer's merchant account).
  • the various pieces of the transaction information may or may not be selected for sharing by the user via the user preferences.
  • a user may agree to share data during a registration process with an application provider (e.g., via an end user license agreement).
  • an application provider e.g., via an end user license agreement.
  • the sharable data may be automatically populated within a third-party message and communicated to an application provider via IP network 312.
  • the application provider Upon receipt of the third-party message, the application provider (e.g., one or more of application providers 338, 339 and 340) may enact a feature provided to a user (e.g., provide a coupon).
  • the application provider may initiate a second transaction (e.g., a piggyback transaction, a statement credit and/or the like).
  • the second transaction may be communicated to ecosystem provider 342 via IP network 312 (e.g., the internet) and processed by ecosystem provider 342 accordingly.
  • ecosystem provider 342 may determine whether a second transaction is permitted and/or forward information associated with the second transaction to another entity (e.g., issuer 320).
  • a GUI may, for example, be rendered onto a display of a user's card or other device (e.g., mobile device 302, user electronic device 345, transaction card 333 and/or contactless device 304).
  • the GUI may display indicia of one or more third-party applications (e.g., provided by one or more application providers 338, 339 and 340) along with summary and/or detailed information. Based upon information gleaned from the information concerning the applications, the user may be better informed as to which third-party applications he or she may wish to associate with his or her powered or non-powered card. Accordingly, the whimsical and festive nature of a user's experience with a GUI rendered by an electronic device may be further enhanced.
  • third-party applications e.g., provided by one or more application providers 338, 339 and 340
  • an application provider may be any entity.
  • ecosystem provider 342 may be an application provider in addition to providing an ecosystem.
  • an application provider may be a third-party application provider and ecosystem provider 342 may host the third party application (e.g., provide coupons).
  • Data sharing may be the same or different based on a particular configuration.
  • FIG. 4 shows device 400 (e.g., a card, a mobile telephonic device, a laptop computer, a desktop computer or an electronic tablet) that may include display 401.
  • Device 400 may include a processor that may render GUI 403 onto display 401.
  • GUI 403 may be an application manager.
  • a user may associate a payment method card (e.g., a powered physical card, non-powered physical card and/or device card) with third party service features within an ecosystem.
  • GUI 403 may be displayed on display 401, for example, a computer monitor, mobile phone touch screen and/or the like.
  • GUI 403 may be, for example, provided as an application for a device (e.g., a computer, a portable computing device and/or a mobile telephonic device) and/or retrieved information from a web browser.
  • An application manager may be provided, for example, on a remote facility and displayed via GUI 403 to allow a user to change the third party service features associated with a card.
  • An application manager may manage an ecosystem of applications and payment method cards, and the user may utilize GUI 403 to, for example, associate a particular feature to a particular payment method card at any time. The user may associate the selected feature with a card and/or a card button.
  • a default feature may be provided and/or that a number of features provided by a card issuer or other entity may be provided in addition to third party service features.
  • a card issuer may provide a card with a default of credit on one button and a default of decoupled debit on a second button. A user may press the first button to perform a credit transaction. A user may press the second button to perform a decoupled debit transaction.
  • GUI 403 may include tabs 405, information 411, virtual card 412, virtual indicia 413 and 414, slider 415, application identifiers 423 and 426, and selection options 428, 431, 432, 441-443 and 446.
  • Virtual card 412 may be provided as a representation of a user's physical and/or device card. A user may be provided with the ability to change between multiple different cards and configure the features associated with those multiple cards. Accordingly, virtual card 412 may be provided with indicia 413 in the configuration of, and indicative of, one button of a user's card, and virtual card 412 may be provided with indicia 414 in the configuration of, and indicative of, another button of a user's card. Indicia 413 and 414 may display the applications currently associated to each button (e.g., an application icon).
  • a slider 415 may be provided to indicate which of applications associated with a button may be a default application (e.g., for online, telephonic and/or non-powered card transactions). Accordingly, a user may, for example, view virtual card 412 in order to refresh the user's memory with respect to the features associated with the buttons on a user's physical and/or device card.
  • a list of applications may be provided on GUI 403. Each application may provide one or more third party service provider features.
  • a user may associate an application providing the feature to the card and/or card button(s). For example, selection 431 may associate application 423 to the button of a card associated with virtual button 413. Selection 432 may associate application 426 to the button of a card associated with virtual button 414. Accordingly, a user may change the features associated to a card by using GUI 403. In order to view the features provided by a particular application the user may, for example, select an "explore" button to view relevant information (e.g., selection 446).
  • the list of applications provided on GUI 403 may be, for example, all applications or a limited subset of all applications available to a user via an ecosystem provider.
  • tab 402 may be selected by a user (e.g., with a keyboard, mouse, touch sensitive screen and/or electronic pointer) to display an application manager home view.
  • a user may select a different tab.
  • tab 403 may be selected by a user to display a featured view including featured applications (e.g., applications-of-the-week).
  • Other tabs may sort applications by category, use and/or the like.
  • Selections 428 may be selections used to activate an application with respect to the user. Activation may include registration with a third party application, acceptance of an end users license agreement associated with the application, and/or the like. Activation may also include selecting a particular feature from among multiple features provided by the application. According to at least one example embodiment, some applications may not require activation (e.g., single feature, non-interactive applications).
  • a user may begin experiencing a selected feature by engaging in card transactions. For example, the user may press a card button associated with a desired feature during a card transaction.
  • a physical and/or device card (not shown) may communicate information indicative of a button that was pressed on the physical and/or device card, along with or separate from other payment data (e.g., an account number, security code, and other data). For example, information indicative of the button that was pressed may be included in discretionary data of a payment message.
  • a payment message may be, for example, one or more tracks of magnetic stripe data (e.g., communicated from a dynamic magnetic stripe communications device), an RFID message (e.g., a near field communication (NFC) message from a radio frequency antenna), and/or an exposed IC chip message (e.g., an EMV message) from an exposed IC chip.
  • magnetic stripe data e.g., communicated from a dynamic magnetic stripe communications device
  • an RFID message e.g., a near field communication (NFC) message from a radio frequency antenna
  • an exposed IC chip message e.g., an EMV message
  • the information indicative of which button was pressed may be passed to a card issuer and/or processor from a point-of-sale and any intermediary devices (e.g., a merchant acquirer processing server).
  • the information may be passed to a remote facility (e.g., a facility providing an application manager) such that the remote facility may determine the button that was pressed by a user.
  • This remote facility may, in turn, retrieve information associated with the third party feature (and/or a feature of a card issuer, processor, application manager provider, and/or any entity) and forward information to that feature provider such that the feature may be performed.
  • Information may additionally and/or alternatively be provided from the feature provider to the entity that provided the information indicative of the button that the user pressed.
  • a non-powered card information indicating that a button was pressed may not be available.
  • information indicative that a purchase was made may be provided to an application manager provider such that the application manager provider can initiate the desired feature for the non-powered card.
  • the feature may be a default feature, a selected feature (e.g., selected using an application manager) and/or a random feature.
  • features may be associated with different types of purchases. For example, one feature may be provided for a particular merchant type (e.g., a grocer's coupon) and another feature may be provided for a different merchant type (e.g., a clothing store coupon).
  • a particular merchant type e.g., a grocer's coupon
  • another feature may be provided for a different merchant type (e.g., a clothing store coupon).
  • Features may be associated with other characteristics of a purchase such as, for example, a purchase above a particular amount (e.g., at or above $100) and/or a purchase below a particular amount (e.g., below $100).
  • additional feature selections are not limited to non- powered cards and may be provided to, for example, users of powered cards and devices.
  • any feature and/or capability not requiring a powered device may be implemented with respect to a non-powered card and any feature and/or capability of a non-powered card may be implemented with respect to a powered card.
  • features and/or capabilities requiring a powered card may be implemented with respect to a non- powered card in various ways. For example, additional functionality may be provided at merchant terminals.
  • GUI 403 may be provided, for example, on a card issuer's and/or application manager provider's website. GUI 403 may be provided, for example, on a bill statement web page.
  • a user may utilize the application manager to manage application features when the user is logged into his/her account.
  • example embodiments described with respect to FIG. 4 may describe a GUI 403 used to make various selections and/or associations, persons skilled in the art will appreciate that other methods are possible. For example, selections may be made by phone, email and/or the like.
  • a third party service provider may utilize GUI 403 as part of a user's administration and/or experience of that third party service.
  • a user's profile page for a third party service may include GUI 403.
  • An application manager provider may provide web- code that retrieves GUI 403 from a remote facility managed by the application manager provider and/or other entity (e.g., issuer, merchant acquirer, payment network, merchant and/or the like).
  • Selection 441 may be utilized by a user to check for updates (e.g., confirm that a feature was changed and/or if any updates are present).
  • Selection 442 may be utilized to explain the functionality of a particular application feature.
  • Selection 443 may be utilized for additional selection options, for example, changing which card is displayed on an application manager.
  • a card may be provided with one button for a particular payment account (e.g., credit) and one button for a changeable feature. Accordingly, a user may, for example, only need to remember one feature associated with a card.
  • a credit account may include rewards, for example, points, cashback, and/or miles, from the card issuer. Accordingly, pushing the payment account button may earn the user such rewards.
  • Pushing the changeable feature button may, alternatively, for example, not earn the user such rewards and may instead initiate a changeable feature. In doing so, for example, the cost of providing a card may be reduced in that the cost of rewards for the card may be reduced.
  • a feature may include, for example, a feature from a third party application provider. The feature from the third party application provider may be, for example, a random reward (e.g., a random coupon).
  • Information 411 may, for example, identify the user and card number associated with virtual card 412 and a corresponding physical card.
  • tabs 405 may provide, for example, a history of purchases made by a user.
  • An application manager may provide indicia reflecting a user rating (e.g., star rating 447).
  • an ecosystem provider may be the same or different from an application manager provider, a remote facility and/or other entities.
  • One or more of the functions described herein as being performed by an application manager provider, and/or other entities, may be performed by the ecosystem provider.
  • an ecosystem provider may act as an application manager provider, application provider, issuer, merchant, third party service provider, payment network and/or the like to provide an end-to-end experience.
  • example embodiments contemplate the same, greater and/or fewer entities, and specific entities are described for purposes of explanation.
  • GUI 403 is provided for purposes of illustration only and may take various forms. For example, features may be associated to a card without buttons and/or a card may include the same, fewer and/or a greater number of buttons than depicted in FIG. 4.
  • FIG. 5 shows device 500 (e.g., a card, a mobile telephonic device, a laptop computer, a desktop computer or an electronic tablet) that may include display 501.
  • Device 500 may include a processor that may render GUI 502 onto display 501.
  • GUI 502 may be an application interface usable to manage a user's experience with an application.
  • GUI 502 may be used to, for example, configure application settings, receive information from an application provider, and/or communicate information to an application provider.
  • GUI 502 may include, for example, application screens 503, 507, 524, 542 and 550, tabs 505, 520, 540 and 545, information displays 510, 513, 523, 525, 527, 530 and 543, and selections 535 and 547.
  • Information display 503 may include, for example, information related to an application provider.
  • information display 503 may display the name and a brief history of the application provider.
  • Tab 505 may be used to display application screen 507 and may include a descriptor associated with application screen 507 (e.g., "How It Works"). Although example embodiments may be described with respect to tabs, persons skilled in the art will appreciate that tabs are used for purposes of explanation only. For example, redirection links may be provided to redirect a user to a configuration screen of an application provider. According to at least one example embodiment, tab 505 may be an information display without tab functionality.
  • Application screen 507 may be a configuration and/or informational screen for an application, and may display information explaining a feature provided by the application.
  • application screen 507 may include information indicating that a coupon will be provided to a user once the user meets or exceeds a performance metric.
  • a coupon may be, for example, a voucher entitling a user to a discount and/or a rebate.
  • the discount and/or rebate may be associated with a particular product, a purchase from a particular vendor and/or the like.
  • a performance metric may define, for example, a transactional event.
  • a performance metric may include a purchase with a card (e.g., a physical and/or device card), a sequence of purchases (e.g., ten purchases) with a card, and/or spending a target amount with a card. Any purchasing and/or non-purchasing transactional event is contemplated by example embodiments.
  • a performance metric may involve a rate of transactions (e.g., checkout 5 books from a library in 10 minutes), a pattern of transactions (e.g., purchase 10 different items from 10 different stores), a target transaction (e.g., purchase a particular item) and/or the like.
  • a rate of transactions e.g., checkout 5 books from a library in 10 minutes
  • a pattern of transactions e.g., purchase 10 different items from 10 different stores
  • a target transaction e.g., purchase a particular item
  • Application screen 507 may include information displays 510 and 513.
  • Information display 513 may include a representation of a type of reward, for example, an image representing a coupon.
  • Information display 510 may display a representation of a performance metric, for example, a monetary value and a payment method. Accordingly, for example, application screen 507 may indicate that a user of a payment method (e.g., a powered card) may receive a coupon and/or increase the value of a coupon each time the user spends an amount indicated in information display 510 using the payment method indicated in display 510.
  • a payment method e.g., a powered card
  • a coupon provided by an application provider may be selected in various ways. For example, a coupon may be randomly selected, may be selected by a user (e.g., from a list of coupons) and/or may be selected based on transactional information (e.g., data related to a purchase, a user purchase history and/or the like). The coupon may be selected prior to or after completion of the performance metric.
  • Each coupon may have a face value (e.g., a normal coupon value) and may be increased in value based on a value of the performance metric (e.g., a value to the application provider). For example, where a performance metric includes spending $100, $200 or $300, a value of the coupon may be 200% at the $100 level, 400% at the $200 level and 800% at the $300 level. A user may or may not select a level of the performance metric (not shown).
  • a face value e.g., a normal coupon value
  • a value of the coupon may be 200% at the $100 level, 400% at the $200 level and 800% at the $300 level.
  • a user may or may not select a level of the performance metric (not shown).
  • Tabs 520 may be used to display application screen 524.
  • Application screen 524 may include, for example, information displays 525, 527 and 530, and selections 535.
  • Information displays 525, 527 and 530 may, for example, display representations of redeemable coupons earned by a user.
  • Selection 535 may be used to change one or more of the coupon representations displayed in application screen 524 (e.g., to cycle through available coupons).
  • a user may, for example, select one of the representations to use the associated coupon for a specific purchase.
  • the coupon may be applied at any time the coupon is usable according to a user selection and/or by default (e.g., a coupon applied to the purchase of a specific product and/or in a specific store as a default).
  • Each of information displays 525, 527 and 530 may display information associated with a coupon in addition to, or alternatively to, the representation of the coupon.
  • the information may include a description of the value provided by the coupon, a description of added value to a base value of the coupon, an expiration date of the coupon and/or any other coupon related information (e.g., within the representation and/or beneath the representation).
  • each representation of a coupon may be a progress meter.
  • a user may build a coupon by selecting various information (e.g., base value, added value, expiration date and/or the like).
  • Tabs 540 may include one or more tabs used to display one or more application screens 542.
  • One of tabs 540 may be used to select an application screen including an information display listing earned coupons.
  • each of information displays 525, 527 and 530 may be selections representing categories of coupons.
  • a user may select information display 525 to display, for example, a list of earned coupons related to food in information display 543.
  • a user may select information display 527 to display, for example, a list of earned coupons related to small appliances in information display 543.
  • a user may select information display 530 to display, for example, a list of earned coupons related to prepared beverages in information display 543.
  • a list of earned coupons may also include, for example, unearned coupons.
  • the unearned coupons may be visually distinguishable from the earned coupons (e.g., a different color and/or shading).
  • Each displayed coupon may be, for example, a selection that may be used to begin earning the coupon, retrieve information associated with the coupon and/or the like.
  • more than one of information displays 525, 527 and 530 may be selected simultaneously.
  • One of tabs 540 may be selected to display a redemption history in information display 543.
  • a redemption history may, for example, display a purchase description and an amount saved.
  • one of tabs 540 may be selected to display a transaction history.
  • a transaction history may include, for example, information indicating a type of transaction (e.g., purchase), an amount spent, a date of the transaction and/or line items indicating that one or more coupons have been earned in relation to the transaction.
  • Tab 545 may selected to display application screen 550.
  • Application screen 550 may include selection 547.
  • a user (having met a performance metric) may activate an earned coupon.
  • a user may select a coupon from among multiple, available coupons and then press selection 547 to render the selected coupon usable.
  • the application provider may randomly select a coupon earned by the user and the user may press selection 547 to render the randomly determined coupon usable.
  • Selection 547 may include an information display (e.g., "$40 spent, press to redeem for coupon").
  • selection 547 may not be included and a coupon may be automatically activated by the application provider (e.g., based on user settings).
  • a user may be notified by an application provider when a coupon is earned and/or additional value is added to the coupon.
  • the application provider may utilize user submitted notification settings to notify the user.
  • a user may activate a coupon for a particular purchase and/or for any purchase (e.g., to be used when applicable).
  • the user may initiate a purchase using a payment method (e.g., powered card) and an activated coupon may be associated to the purchase (e.g., manually and/or automatically associated to the purchase).
  • a payment method e.g., powered card
  • an activated coupon may be associated to the purchase (e.g., manually and/or automatically associated to the purchase).
  • an application provider may receive transactional data indicating a type of product and/or a location of a purchase, search a list of coupons earned by a user and associate any applicable coupons to the purchase based on the transactional data.
  • value may be provided to the user (e.g., via a statement credit), for example, immediately, at authorization, at settlement and/or in a number of days.
  • the application provider may attach the coupon and/or a number associated with the coupon, for example, to an email.
  • a user may print the coupon and/or use number associated with the coupon (e.g., for an internet purchase).
  • notification and reward fulfillment methods may be used.
  • a user may be notified of a reward or receive a reward via email, telephonic data transfer (e.g., text messaging), telegram and/or the like.
  • no notification may be provided and/or a user may be required to retrieve a coupon (e.g., via a GUI).
  • a coupon may be transmitted to a user's powered card and the powered card may be operable to display a barcode usable at, for example, a retail establishment.
  • a selection may be included to activate functionality by which outright purchases of a coupon and/or contributions towards a coupon may be made (not shown). Purchases and/or contributions may be made using, for example, piggyback charges, third party charges, direct purchases and/or the like.
  • a piggyback charge may be a statement debit (charge) added to a user statement, for example, for each purchase using a card and/or a device card.
  • a user may select an amount and/or frequency of the piggyback charge using, for example, GUI 502 (not shown).
  • GUI 502 not shown.
  • a user may earn a coupon and/or increase the value of a coupon for each piggy back charge.
  • a third party charge may be a monetary value provided by an application provider, for example, upon a user meeting an incentive performance metric in addition or alternatively to using the payment method (e.g., making purchases at a specific store and/or buying a specific product).
  • a direct purchase may be a partial or complete purchase of a feature by a user that is not attached to any other purchase.
  • a vendor may provide functionality by which a user may swipe a card and/or otherwise communicate data of a card to partially or wholly purchase a coupon without also purchasing any item from the vendor.
  • GUI 502 may include a blank information display (not shown).
  • a feature provider may provide 'drag-and-drop' coupon icons (e.g., on a feature provider website) representing the reward.
  • a user may drag the icon onto GUI 502 and GUI 502 may be automatically modified to include the coupon.
  • the icon transfer may include feature provider information, for example, information invisible to a user that may be used by an application.
  • the coupon provider may provide special incentives for a limited time (e.g., Black Friday), as a customer acquisition tool, as a customer retention tool, and/or the like.
  • GUI 502 may display a configurable coupon application.
  • a user may select from coupons provided by different retail outlets. The user may drag an icon from a webpage of a particular retail outlet onto the configurable application. The user may drag an icon from a webpage of a different retail outlet onto the configurable application. Both icons may appear on the configurable application. Accordingly, an application may not be limited to a specific retailer and/or coupon provider, and may enhance the whimsical and festive nature of a feature provided to a user.
  • An application accessed using GUI 502 may include configurable functionality to improve a user experience. For example, a representation of each coupon earned by the user may be publically and/or privately displayed when earned (and/or a progression display may be updated). For example, coupon information may be displayed on a user's social networking page, on a physical display at chosen location and/or the like.
  • an application provider and/or an application of an application provider may be associated to the user during, for example, an activation process. A user requesting access to an application may be prompted for information. The information may include, for example, security credentials used to access a social networking site associated with the user.
  • Selections may, for example, activate an additional and/or alternative feature.
  • a selection (not shown) may be used to pay an amount corresponding to completion of the performance metric displayed in information display 510.
  • the amount may be, for example, immediately charged via GUI 502 and/or may be attached as a piggyback charge to a purchase (e.g., a next purchase using a card and/or a device card). Accordingly, a user may take advantage of limited time offers even where the user does not expect to complete a performance metric within the limited time. The whimsical and festive nature of a coupon application may therefore be enhanced.
  • FIG. 38 shows process flow chart 600.
  • An application provider may receive user configuration selections (e.g., as in step 610) and transactional data from, for example, an application manager provider (e.g., as in step 620). The application provider may associate the transactional data with a user and determine if a performance metric has been completed (e.g., as in step 630). If a performance metric has not been completed, the application provider may update one or more information displays based on the received transactional data (e.g., as in step 640). If a performance metric has been completed, the application provider may display a completion message to a user and update one or more information displays (e.g., as in step 650). A value (e.g., coupon) may be transmitted to, for example, the payment method user (e.g., as in step 660).
  • a value e.g., coupon
  • a coupon provider may receive a user feature selection.
  • the coupon provider may receive transactional information, for example, information indicative of a feature selected by a user (e.g., via a telephone device card, powered card and/or the like) and transactional information related to a payment card (e.g., a number of transactions performed by the user with the payment card, an amount spent and/or the like).
  • transactional information for example, information indicative of a feature selected by a user (e.g., via a telephone device card, powered card and/or the like) and transactional information related to a payment card (e.g., a number of transactions performed by the user with the payment card, an amount spent and/or the like).
  • the coupon provider may determine if a performance metric has been completed.
  • a performance metric may include ten user purchases using a powered credit card.
  • a progression display (e.g., a progress meter) may be updated (e.g., if applicable). If the transactional metric has been met, an email may be sent notifying the user that the coupon has been earned. One or more progression displays may be updated and the coupon may be communicated to the user. According to at least one example embodiment, the notification and coupon may be communicated to the user in the same email message.
  • a coupon code may be communicated to the user.
  • a user may be notified that a coupon code and/or a coupon is available electronically (e.g., accessed from an application manager).
  • FIG. 39 shows device 700 (e.g., a card, a mobile telephonic device, a laptop computer, a desktop computer and/or an electronic tablet) that may include display 701.
  • Device 700 may include a processor that may render GUI 702 onto display 701.
  • GUI 702 may be an application interface usable to manage a user's experience with an application.
  • GUI 702 may be used to configure application settings, receive information from an application provider, communicate information to an application provider and/or the like.
  • GUI 702 may include, for example, tabs 703, 718, 730 and 763, application screens 707, 723, 752 and 773, information displays 710, 713, 715, 727, 733, 737, 740, 743, 753, 755, 757 and 760, progress meter 725, entry fields 767 and 775, and selections 765, 770 and 777.
  • Tab 703 may be used to display application screen 707 and may include a descriptor associated with application screen 707 (e.g., "How It Works"). Upon selecting tab 703, application screen 707 may be displayed to a user.
  • Application screen 707 may be a configuration screen for an application and may include information explaining features provided by the application.
  • application screen 705 may display different configurable, selectable features, along with explanatory information associated with each feature.
  • application screen may not be a configuration screen and may be an information screen.
  • a feature may not be configurable and/or selectable (e.g., a set feature) and static feature information may be displayed.
  • a feature provided by an application may provide a user selected reward once a user meets or exceeds a performance metric.
  • a feature provided by an application may provide a random reward from a collection of rewards once a user meets or exceeds a performance metric.
  • the reward may be provided by the application provider upon a user meeting or exceeding the performance metric.
  • An example of a performance metric may include a user completing one or more purchases meeting or exceeding a monetary value using a payment card.
  • a feature provided by an application provider may be represented by, for example, information displays 710, 713 and 715.
  • information display 713 may display an image representing a collection of different rewards.
  • Information display 710 may display information associated with a performance metric.
  • the performance metric may be, as one example, a transactional based performance metric represented by an image of a payment card and a monetary value.
  • Information display 715 may include information associated with the performance metric and/or the collection of rewards. For example, information display 715 may notify a user that shopping at a particular store will earn additional rewards, and/or notify a user as to the odds of winning any one of the rewards from the collection of rewards.
  • application screen 707 may include information describing that a user may earn one random reward from a collection of rewards upon spending at least a monetary value (e.g., $6,000) using a payment method (e.g., a smartphone payment card). If the payment method is used to make purchases from a store (e.g., a particular store associated with the application) the amount spent in order to earn the reward may be reduced (e.g., earn a reward twice as fast).
  • a payment method e.g., a smartphone payment card
  • application screen 723 may be displayed to a user.
  • Application screen 723 may include progress meter 725 and information display 727.
  • Progress meter 725 may indicate user progress towards completing a performance metric.
  • Progress meter 725 may be any type of progress meter.
  • a progress meter may be represented as a thermometer with a temperature scale replaced by a monetary scale (e.g., $0- $6,000).
  • a user may gauge progress towards a reward.
  • Information display 727 may, for example, display an exact amount spent towards earning the reward.
  • a type of progress meter 725 is not limited.
  • an application provider may be an actress named 'Dynama Lemon.'
  • the application provider may display a representation of a lemon.
  • the representation may be, for example, a black and white outline.
  • the representation of the lemon may be progressively colored-in to demonstrate progress.
  • application screen 752 may be displayed to a user.
  • Application screen 752 may provide details with respect to the representation of the collection of rewards displayed in information display 713, and may include, for example, information displays 737, 740, 743, 753, 755, 757 and 760.
  • Information displays 737, 740 and 743 may each display a representation of, for example, a coupon (e.g., different coupons) and information related to each coupon (e.g., an additional value associated with a coupon when the payment method is used to buy specific products).
  • Information displays 753, 755, 757 and 760 may each display a representation of a tangible item and a description of the tangible item.
  • the coupons and tangible items may be a collection of rewards from which a reward may be randomly awarded to the payment method user upon completion of the performance metric.
  • Selection 765 may be a redemption button that may be used upon completion of the performance metric to receive the random reward.
  • a user may change, for example, notification settings before using selection 765.
  • a user may be awarded a random reward from among coupons and tangible items.
  • coupons may include a coupon providing 5% off purchases of a product, $50 off purchases of $500 or more, 15% off purchases from a specific store and/or retailer, and/or the like.
  • tangible items may include a makeup kit, a purse, nail polish remover, a ring and/or the like. Each item may be, for example, exclusively available to users of the payment method.
  • Tab 763 may be associated to notification settings. For example, tab 763 may be selected by a user to display entry fields 767 and 775, and selections 770 and 777. Entry fields 767 and 775 may be used by a user to enter information related to the type of notification (e.g., an email address and/or a text message number). Selections 770 and 777 may be used to submit the information entered into entry fields 767 and 775, respectively.
  • information related to the type of notification e.g., an email address and/or a text message number.
  • Selections 770 and 777 may be used to submit the information entered into entry fields 767 and 775, respectively.
  • a user may be notified by the application provider when a reward is earned.
  • the application provider may utilize user submitted notification settings to notify the user. For example, a user may submit an email address using entry field 767 and selection 770. As another example, a user may submit a number (e.g., a telephone number for text messaging) using entry fields 775 and selection 777.
  • a notification email and/or text message may be sent to the email and/or number when a reward is earned.
  • the email and/or text message may include a message indicating that a reward has been earned and that a redemption code usable to retrieve the reward is available.
  • the application provider may attach the redemption code and/or reward to the notification (e.g., embedded in the email).
  • electronic rewards may be downloaded by clicking, for example, an information display associated with the earned reward (e.g., using an application manager).
  • example embodiments are described with respect to email and/or text messaging, persons of ordinary skill in possession of example embodiments will appreciate that many different notification methods may be used (e.g., telephonic, text messaging, telegram and/or the like). According to at least one example embodiment, no notification may be provided. According to other example embodiments, a user may provide a physical address at which to receive notifications and tangible rewards.
  • a user may submit multiple addresses (e.g., one or more email addresses, one or more telephone numbers, and/or one or more physical addresses) and select one of the addresses prior to redemption such that each reward redemption may result in a different notification or fulfillment (e.g., different rewards and/or notifications may be sent to different addresses at the whim of the user).
  • addresses e.g., one or more email addresses, one or more telephone numbers, and/or one or more physical addresses
  • example embodiments described in relation to FIG. 7 may include performance metrics based on a monetary value
  • various other performance metrics are within the scope of example embodiments (e.g., number of transactions, type of transactions, a user acting as a merchant using a particular merchant service and/or the like).
  • FIG. 40 shows device 800 (e.g., a card, a mobile telephonic device, a laptop computer, a desktop computer or an electronic tablet) that may include display 801.
  • Device 800 may include a processor that may render GUI 802 onto display 801.
  • GUI 802 may be an application interface usable to manage a user's experience with an application.
  • GUI 802 may be used to configure application settings, receive information from an application provider, communicate information to an application provider and/or the like.
  • GUI 802 may include, for example, tab 805, application screen 807, information displays 810, 820, 830 and 840, and selection 850.
  • Tab 805 may be used to display application screen 807 and may include a descriptor associated with application screen 807 (e.g., "Scratch Off"). Upon selecting tab 805, application screen 807 may be displayed to a user. Application screen 807 may be an interactive selection screen for an application.
  • a descriptor associated with application screen 807 e.g., "Scratch Off”
  • a feature provided by an application may provide a user an opportunity to select one reward from among multiple, hidden rewards.
  • a user may be presented with multiple representations of a logo (e.g., an application provider logo) in information displays 810-840.
  • the user may be provided the opportunity to select one of information displays 810- 840 to unveil a reward.
  • a user may select information display 820 to reveal that the user has won a coupon (e.g., 15% off of a purchase).
  • a user may select two or more of information displays 810-840 and receive a reward associated with each selection.
  • multiple performance metrics may be available to the user.
  • a value e.g., cost to the user and/or value provided to the application provider
  • a different number of selection may be made (e.g., one selection for $50 in spends, two selections for $100 in spends, etc.).
  • an application provider may receive a monetary value from, for example, an ecosystem provider, an issuer, a merchant and/or a payment network in exchange for providing a reward to a user.
  • the monetary value may be, for example, a number of basis points (1/100 of a percentage point) related to a transaction.
  • an application provider may not receive a monetary value and/or may provide value.
  • the application provider may receive value, for example, via customer acquisition, retention of customers, marketing (e.g., visibility within an ecosystem) and/or the like.
  • a value provided via a coupon may be greater than a monetary value provided to a coupon provider.
  • a difference in value may be offset by other factors (e.g., high value coupons where 90% of the coupons are expected to expire prior to use).
  • a performance metric may be based on transactional processing.
  • Transactional processing may include multiple stages.
  • a credit transaction may include authorization, batching, clearing and funding.
  • An application and/or feature provider may provide a reward to a user at one of the various stages of transaction processing (e.g., authorization).
  • a transaction may be reversed (e.g., a void or credit) after a user receives a reward based on the transaction. For example, a user may purchase an item, receive an electronic reward and then return the purchased item.
  • the application and/or feature provider may be notified by the application manager provider that a transaction has been reversed.
  • a application and/or feature provider may take action based on the notification, for example, provider may reclaim a coupon, invalidate a coupon code, remove user authorization to use an application and/or feature, establish a debit pool that must be reduced by future uses of the payment method before additional rewards may be earned and/or the like.
  • a reward may be granted to a user at a stage of transaction processing (e.g., authorization) but may not be available for use by the user until a different stage of processing (e.g., settlement).
  • a transaction is reversed (e.g., via a return, a charge-off and/or a charge-back) after being made available to the user the application and/or feature provider may take steps to remove a value associated with the coupon. Accordingly, if a card is used fraudulently (e.g., a stolen card), rewards may be disassociated with a reward system when the purchases are charged-off as a result of the fraudulent spend.
  • a card is used fraudulently (e.g., a stolen card)
  • rewards may be disassociated with a reward system when the purchases are charged-off as a result of the fraudulent spend.
  • FIG. 41 shows process flow chart 900.
  • a rewards provider may utilize an application to configure rewards (e.g., for a rewards or loyalty program).
  • a computing device e.g., a server
  • reward description details may be defined (e.g., as in step 910).
  • a rewards provider may select a type of reward, enter a name for the reward, provide a brief description of the reward and upload an image to represent the reward.
  • the reward type may be, for example, a coupon, an item, a virtual item, cashback, points, miles, entry into a lottery, and/or any other type of reward. Once a reward type is selected, the GUI may display further options tailored to the type of reward.
  • a rewards provider may define reward execution details (e.g., as in step 920).
  • a coupon provider may determine the type of coupon that will be provided to users by selecting various options. The options may determine, for example, whether or not the coupon will be based on a purchase amount or a purchased product, and the type of discount or rebate to be applied. If the coupon will be based on a purchase amount, the type of discount or rebate may include, for example, a percentage or value based discount. If the coupon will be based on a purchased product, the type of discount or rebate may include, for example, a percentage discount, a value based discount or a replace value.
  • a rewards provider may set distribution limits for the rewards program (e.g., as in step 930).
  • the distribution limits may define the financial liability that may be incurred by the rewards provider.
  • a coupon provider may limit the number of coupons that are distributed and/or the maximum value of the coupons (e.g., the value either individually or in aggregate).
  • a rewards provider may set an overall distribution limit of 1000 coupons and a per customer distribution limit of 5 coupons.
  • a rewards provider may define reward execution requirements (e.g., as in step 940).
  • Reward execution requirements may, for example, describe the circumstances under which a coupon is redeemable.
  • coupons redemption may be limited to online purchases or store purchases, or permitted for both store purchases and online purchases.
  • in-store redemption is permitted, the redemption may be limited to a particular store, a set of particular stores, and/or one or more geographical areas (e.g., by zip code, province/state and/or country).
  • Information that may be entered into a GUI by a rewards provider may include, for example, one or more store ID's, store names, zip codes, province/state information and/or country codes.
  • reward redemption may be limited to one or more retailers (e.g., Dynamo Sporting Goods), to one or more types of retailers (e.g., sporting goods), by maximum and/or minimum purchase thresholds (e.g., purchase amount thresholds), by duration (e.g., a range of dates), by date (e.g., specific days), by time (e.g., specific hours), and/or by product and/or product group (e.g., to one or more SKU groups).
  • retailers e.g., Dynamo Sporting Goods
  • types of retailers e.g., sporting goods
  • maximum and/or minimum purchase thresholds e.g., purchase amount thresholds
  • duration e.g., a range of dates
  • date e.g., specific days
  • time e.g., specific hours
  • product and/or product group e.g., to one or more SKU groups
  • coupon redemption may be circumscribed by, for example, location, commercial relationships, cooperative interests, and/or logistical considerations.
  • a retailer may increase traffic through stores at historically underperforming times, days or months, reduce percentage reduction liability that may occur for higher value purchases, and restrict coupons to particular products, manufacturers or types of manufacturers.
  • a retailer with knowledge of customer loading patterns within its stores may limit coupon redemption to particular stores at particular times on particular dates to level workload, control local traffic, synergize with staffing levels and/or increase loading at underperforming stores or regions.
  • a rewards provider may define reward usability and compatibility (e.g., as in step 950).
  • a retailer may define how coupons are used together (coupon usability), define the types of payment methods that are usable during a qualifying purchase (purchase types), and/or define the transferability of the coupons (user restrictions).
  • defining coupon usability may include selecting whether coupons are usable with all other coupons, with specific coupons or only by themselves.
  • Defining purchase types may include selecting payment methods with which a coupon may be used, for example, all payment methods, specific branded payment methods (e.g., store loyalty credit card), cash, prepaid cash, payment methods supported by specific payment networks (e.g., Visa, MasterCard, Discover and/or American Express) and/or the like.
  • Defining user restrictions may include restricting redemption to a designated user or designated users (e.g., the user to whom the coupon was sent) or permitting redemption by any user (e.g., a transferable coupon).
  • process flow chart 900 includes arrows, the arrows are not limitations of order. Persons of ordinary skill in the art will appreciate that some or all of the described activities may be completed sequentially, in a different order or simultaneously. Although process flow chart 900 may be described above with respect to coupons, persons of ordinary skill in possession of example embodiments will understand the described process to be broadly applicable to various types of rewards. Persons of ordinary skill will understand that whether a process is described with respect to selection or entry, a selection may be implemented with an entry, an entry with a selection, and other possibilities exist (e.g., pulling SKUs from a database or other file).
  • FIG. 42 shows process flow chart 1000.
  • a rewards provider may utilize an application to configure a loyalty program.
  • a computing device e.g., a server
  • a reward provider may define a description of a loyalty program (e.g., as in step 1010).
  • a rewards provider may select a program type, enter a name for the loyalty program, provide a brief description of the loyalty program and identify one or more rewards provided by the loyalty program.
  • the program type may be, for example, a predefined type of loyalty program. Once a reward type is selected, the GUI may display further options tailored to the type of loyalty program.
  • a rewards provider may define one or more reward distribution criteria (e.g., as in step 1020).
  • a loyalty program may provide a reward based on a monetary value spent (e.g., number of dollars), a number of visits (in-store and/or online), a number of particular items purchased and/or a number of purchases.
  • a selection to base a loyalty program on monetary value may include entering an amount of the monetary value at which a reward may be provided.
  • a selection to base a loyalty program on a number of visits may include entering the number of visits before a reward may be provided, and may include entering a number of consecutive days on which the visits must occur (e.g., a date range or a number).
  • a selection to base a loyalty program on a number of purchased items may include entering one or more item types, one or more stock keeping units (SKU), and/or entering a number representing the number of items to be purchased before a reward may be provided.
  • a selection to base a loyalty program on a number of purchases may include entering a number representing the number of purchases before a reward may be provided, and may include entering a minimum spend amount per purchase.
  • a rewards provider may set a rewards distribution criteria period for the loyalty program (e.g., as in step 1030).
  • the distribution criteria period may specify a time period in which the loyalty program is deemed to be active and rewards may be earned.
  • a rewards provider may select an option to provide rewards from program inception or enter a date range.
  • a rewards provider may apply a retroactive time period such that historical data may be used to determine whether a reward was earned (e.g., prior to inception of the program).
  • a rewards provider may set program earning time constraints with respect to the loyalty program (e.g., as in step 1040). For example, reward earning may be limited such to only specific days, and/or specific days and times.
  • a loyalty program may be implemented to provide loyalty rewards for customers shopping on Black Friday (e.g., November 28, 2014) during non-peak hours.
  • a rewards provider may define program run limits (e.g., as in step 1050). For example, a rewards provider may select one or more options that may include running a loyalty program until start and end dates have been met (e.g., a date range), a particular amount of rewards have been generated, a particular amount of rewards have been redeemed, a particular amount of value has been generated and/or a particular amount of value has been redeemed.
  • start and end dates e.g., a date range
  • a rewards provider may define program distribution criteria (e.g., as in step 1060). For example, a rewards provider may elect to distribute rewards only to a particular segment of a customer or consumer base. Rewards may be distributed based on psychographics, for example, any personality trait, value, attitude, interest, and/or lifestyle choice (e.g., "gamers,” “savers,” “sportsters,” and/or “child conscience parents”). Award distribution may be based on, for example, gender, age, income and/or products (e.g., one or more SKUs). For example, coupons for geriatric feminine products may be distributed to female consumers by selecting gender and age as a basis for distribution, and entering product SKUs corresponding to the geriatric feminine products.
  • process flow chart 1000 includes arrows, the arrows are not limitations of order. Persons of ordinary skill in the art will appreciate that some or all of the described activities may be completed sequentially, in a different order or simultaneously. Although process flow chart 1000 may be described above with respect to coupons, persons of ordinary skill in possession of example embodiments will understand the described process to be broadly applicable to various types of rewards. Persons of ordinary skill will understand that whether a process is described with respect to selection or entry, a selection may be implemented with an entry, an entry with a selection, and other possibilities exist (e.g., pulling SKUs from a database or other file).
  • FIG. 43 shows process flow charts 1100 and 1150.
  • a rewards provider may utilize an application to test a loyalty and/or rewards program by providing rewards to all, or one or more segments of, identified consumers (e.g., customers) and monitoring the effect of the reward.
  • the effect of the reward may be determined via test result data in multiple ways and may depend on the reward. For example, if a coupon is offered as a reward, transaction data and/or coupon-use data may be monitored to determine if the coupon resulted in a change in consumer behavior. The data may be collected at one stage of transaction processing (e.g., authorization, settlement, and/or the like), each stage or any combination of stages.
  • transaction data and/or coupon-use data may be monitored to determine if the coupon resulted in a change in consumer behavior.
  • the data may be collected at one stage of transaction processing (e.g., authorization, settlement, and/or the like), each stage or any combination of stages.
  • test result data may include segment data from one or more segments receiving a coupon, from one or more segments not receiving a coupon and/or from one or more segments receiving a different coupon (multi-segment testing).
  • Test results may include data from a portion of a segment receiving a coupon and a portion of a segment not receiving a coupon (in-segment testing).
  • Test result data may include data from an entire consumer base (global testing).
  • segment data e.g., in-segment and/or multi- segment data
  • before-and-after data may be compared (in- segment, multi-segment and/or global) using collected and historical data.
  • a computing device may display an interactive GUI that is usable to describe and/or define test and distribution criteria used in program testing (e.g., as in step 1110).
  • a rewards provider may select a loyalty or rewards program for testing, enter a name of the test, enter a brief description, enter a number of rewards to generate, and/or select a percentage or number of consumers (e.g., customers and/or non-customers) to receive the generated rewards.
  • the selected percentage or number may be applied to an entire consumer base (e.g., 100% where no segments are defined), to segments of a consumer base (e.g., x% where multiple segments are defined) and/or to a single segment of a consumer base (e.g., x% where a single segment is defined).
  • Individual segments may be, for example, defined by distribution criteria.
  • a rewards provider may define one or more segments to be used in program testing be selecting or entering distribution criteria (e.g., as in step 1120).
  • a segment may be based on, for example, psychographics.
  • Psychographics may include any personality trait, value, attitude, interest, and/or lifestyle choice (e.g., "gamers,” “savers,” “sportsters,” and/or “child conscience parents”).
  • a segment may be based on characteristics or goods, for example, gender, age, income and/or products (e.g., one or more SKUs). Consumer psychographics and characteristics may be entered by a user and/or determined from transactional data.
  • test may be initiated (e.g., as in step 1130).
  • the coupons may be distributed and data collection begun (e.g., via routing of transaction messages to a remote facility or other entity).
  • data may be analyzed and results may be provided.
  • Graphs may be displayed to summarize the test results.
  • a test may be repeated one or more times and graphical data may be continuously updated. Repetition may provide temporal or event based effect information (e.g., seasonal habits or the effects of weather).
  • tests may be triggered based on events to determine their impact on consumer habits (e.g., geographic testing triggered by a catastrophe).
  • a computing device may display an interactive GUI that is usable to simulate a loyalty program or rewards program.
  • a rewards program may be built and simulated to ensure that the rewards program functions according to the reward provider's intended design.
  • a rewards provider may select a loyalty or rewards program (e.g., as in step 1160).
  • the reward program may be selected using the reward description (e.g., "incentive coupon").
  • the program may be, for example, selected from a list of programs. If the coupon includes a barcode, the type of barcode may be selected.
  • a coupon simulation type may be selected.
  • a coupon simulation type may be, for example, a valid coupon or a test coupon.
  • An address e.g., email address) of a user and a mail server identification may be entered.
  • the program may be simulated (e.g., as in step 1170) by, for example, selecting to send one or more test emails (e.g., in a case where coupons are distributed by email), or by entering condition settings and selecting to simulate the program based on the condition settings.
  • a condition may include, for example, maximum liability.
  • the simulation may determine, based on the rewards program, the maximum liability where the maximum number of coupons are distributed and used. Alternatively, percentage of use assumptions and the like may be entered to determine a resulting liability based on the assumptions.
  • conditions may include any parameter used to determine the result of a defined rewards or loyalty program.
  • process flow charts 1100 and 1150 include arrows, the arrows are not limitations of order. Persons of ordinary skill in the art will appreciate that some or all of the described activities may be completed sequentially, in a different order or simultaneously. Although process flow charts 1100 and 1150 may be described above with respect to coupons, persons of ordinary skill in possession of example embodiments will understand the described process to be broadly applicable to various types of rewards. Persons of ordinary skill will understand that whether a process is described with respect to selection or entry, a selection may be implemented with an entry, an entry with a selection, and other possibilities exist (e.g., pulling SKUs from a database or other file).
  • FIG. 44 shows process flow charts 1200 and 1250.
  • Process flow chart 1200 may provide an example of the implementation of a rewards program and process flow chart 1250 may provide an example of the implementation of a loyalty program.
  • a computing device may display an interactive GUI usable to define a rewards program (e.g., as in step 1205).
  • a remote facility may receive rewards program configurations (e.g., as in step 1210) from, for example, a third party provider (e.g., a retailer). Based on the defined program, the remote facility may distribute rewards according to the program definition. For example, the remote facility may distribute coupons to all customers within a demographic (e.g., globally, by segment, by partial segment and/or the like).
  • the rewards may be distributed physically (e.g., by mail, courier, in-store and/or the like) and/or non-physically (e.g., via electronic mail, telephonically, SMS messaging, television, social networking and/or the like).
  • a server of a remote facility may receive or pull data from a server of a third party provider, and based on the data distribute coupons to consumers via electronic mail.
  • the remote facility may receive reward redemption information (e.g., as in step 1220).
  • the third party provider may communicate coupon redemption information to a remote facility (e.g., an ecosystem provider), and/or the remote facility may receive transactional data from one or more network entities in a transactional flow.
  • the transactional data may include, as one example, an authorization message.
  • the reward redemption information may include, for example, coupon identification information, user information, location information, product information, establishment information (e.g., store ID), purchase price information, and/or any other transactional data.
  • the remote facility may determine if the coupon is valid based on the reward redemption information and a rewards program.
  • the remote facility may, for example, determine if the coupon is recognized as active for a rewards program, and if the coupon redemption meets the requirements of a rewards program.
  • a rewards program may provide a discount that is only valid at a particular store, on a particular date and for a particular user.
  • the remote facility may receive an authorization message that includes identification of a coupon and determine if the coupon is active for any rewards program. If the coupon is active, the remote facility may compare received transactional information against the requirements for the rewards program.
  • the remote facility may provide validation information (e.g., as in step 1225) to a third party provider, a merchant terminal, an issuer, and/or other entity. For example, if the coupon is active and the transaction complies with the requirements of a rewards program, the remote facility may communicate information indicating that the discount or rebate may be applied to the transaction. If the coupon does not meet one or more criteria for redemption, the remote facility may indicate that the discount or rebate should not be applied to the transaction.
  • validation may occur after a purchase, for example, based on settlement.
  • a computing device e.g., a server
  • a remote facility may receive loyalty program configurations (e.g., as in step 1260) from, for example, a third party provider (e.g., a coupon provider).
  • a third party provider e.g., a coupon provider
  • the remote facility may receive transaction data. Based on the transaction data, historical data and a loyalty program definition, the remote facility may determine loyalty program applicability and performance metric status (e.g., as in step 1265).
  • a server of a remote facility may receive or pull data from a server of a third party provider, or receive transactional messages from an entity within a purchase flow (e.g., as described with respect to FIG. 35).
  • the transactional data may evaluated to determine if a loyalty program applies.
  • a loyalty program may award a coupon to users of a particular loyalty credit card that fall within a particular demographic.
  • the remote facility may evaluate the transactional data to determine if a performance metric has been met.
  • the performance metric may include completing 10 purchases of a particular product using the loyalty credit card.
  • the historical data may indicate that the user has previously purchased the particular product 9 times and the current purchase completes the performance metric.
  • a reward may be distributed as defined in the loyalty program (e.g., as in step 1270). If the performance metric has been met, a discount may be automatically applied to the transaction by communicating a message (e.g., to a point-of-sale device) and/or a coupon may be communicated to the user.
  • a message e.g., to a point-of-sale device
  • the remote facility may receive reward redemption information (e.g., as in step 1275) upon use of the coupon.
  • the third party provider may communicate coupon redemption information to the remote facility, and/or the remote facility may receive transactional data including reward redemption information from one or more network entities in a transactional flow.
  • the transactional data may include, as one example, an authorization message.
  • the reward redemption information may include, for example, coupon identification information, user information, location information, product information, establishment information (e.g., store ID), purchase price information, and/or any other transactional data.
  • the remote facility may determine if the coupon is valid based on the reward redemption information and the loyalty program definition.
  • the remote facility may, for example, determine if the coupon is recognized as active for a loyalty program, and if the coupon redemption meets the requirements of the loyalty program.
  • the loyalty program may provide a discount or rebate that is only valid when used during specific hours in a particular country.
  • the remote facility may receive a message (e.g., a settlement message) that includes identification of a coupon and determine if the coupon is active for any loyalty program.
  • the remote facility may compare the received transactional information against the requirements for the rewards program. For example, the remote facility may determine if the coupon is being used during the specific hours and in the particular country, as required by the loyalty program. If the coupon is active and the requirements of the loyalty program are met, the coupon may be determined valid. Otherwise, the coupon may be determined invalid.
  • the remote facility may provide validation information (e.g., as in step 1280) to a third party provider, a merchant terminal, an issuer, and/or other entity. For example, if the coupon is valid, the remote facility may communicate information indicating that the discount or rebate may be applied to the transaction. If the coupon is not valid, the remote facility may indicate that the discount or rebate should not be applied to the transaction.
  • validation may occur, for example, at authorization (or any other stage of processing).
  • process flow charts 1200 and 1250 include arrows, the arrows are not limitations of order. Persons of ordinary skill in the art will appreciate that some or all of the described activities may be completed sequentially, in a different order or simultaneously.
  • process flow charts 1200 and 1250 may be described above with respect to coupons, persons of ordinary skill in possession of example embodiments will understand the described processes to be broadly applicable to various types of rewards. Persons of ordinary skill will understand that if a process is described with respect to selection or entry, a selection may be implemented with an entry, an entry with a selection, and other possibilities exist (e.g., pulling SKUs from a database or other file). According to example embodiments, cards, ecosystems, third party applications, testing, simulation and transaction flows may be included in the implementation of a reward or loyalty program.
  • Example embodiments described with respect to process flow charts 1200 and 1250 are not limiting of example embodiments, but serve as examples.
  • Various transactional flows and systems may be implemented in various ways (e.g., as described with respect to FIG. 3). Although specific entities may be used to describe example embodiments in relation to FIG. 12, various entities may perform one or more functions of other entities, and the particular entities used to describe
  • FIG. 12 are not limiting.
  • a value document may be used to generate demographic information to understand consumer behavior by providing, for example, incentives to purchase, reductions in the price of particular items, free samples, and/or the like.
  • a value document may provide free shipping, buy-one get-one, trade-in for redemption, a coupon for a first-time customer, free trial offer, launch offer, special event offer and/or free giveaway.
  • a value document may be, for example, a coupon providing $5.00 off a $10.00 purchase, and the coupon may be represented by a two or three dimensional barcode.
  • a price conscious consumer may, for example, present a coupon to check out at a merchant, and the merchant may retain the coupon and offer the consumer a loyalty card during the check-out process. Consumer acceptance of the loyalty card may be low.
  • a value system may issue an value identifier to influence consumer behavior for loyalty or advanced coupon features.
  • a value system may provide a multistage value account identifier which is individualized based on use of the multistage value account identifier.
  • the multistage value account identifier may be, for example, a single code (e.g., represented by a barcode).
  • the multistage value identifier may be associated to a multistage value account.
  • the multistage value account may or may not be associated with a particular user.
  • a multistage value account may be associated with a defined or undefined set of stages.
  • a stage may require, for example, a particular action (e.g., a purchase or a game move). For example, at a first visit to a retailer, a user may present a multistage value account identifier to receive $5.00 off a $10.00 purchase, and at a second visit receive $10.00 off a $20.00 purchase, and at a third visit receive $15.00 off a $20.00 purchase and at a fourth visit receive a free sandwich along with a message announcing that the user of the multistage value account identifier has achieved status and will be provided a card (e.g., gold status card) upon providing user information (e.g., a telephone number, email address, physical address and/or other information associated with the consumer).
  • a card e.g., gold status card
  • the card may, for example, represent a conventional loyalty program, specific privileges and/or expand the benefits provided by the multistage value system (e.g., with increasingly individualized customization based on information obtained from redemption associated with the stages of the multistage value account and/or based on user information).
  • User information may be requested via, for example, a retailer POS system, a method specified by the POS system, a receipt and/or an online purchase confirmation.
  • a user may receive an advertisement including a multistage value account identifier or method of obtaining a multistage account identifier, along with information indicating that upon achieving a particular stage the user is eligible for a status card upon submitting user information (e.g., to a website URL).
  • use of a multistage value account identifier may be conditioned on consent by the user for access to user information, for example, user information stored by a merchant, acquirer, issuer, processor, payment network, third party service provider, remote facility, device provider, mobile service provider and/or any other entity.
  • a multistage value system may be an implementation of an abbreviated (mini) loyalty program or an introductory loyalty program and a user may be seamlessly converted from the multistage value account to a value program.
  • a user may be converted to a loyalty card representing an extension of the multistage value system, or a different and/or traditional loyalty program. Consumer acceptance of the loyalty card may be increased and/or high as compared to conventional program offerings at checkout.
  • one or more stages of a multistage value account may expire. According to other example embodiments, no stage of a multistage value account expires. According to still other example embodiments, one or more stages of a multistage value account may include a change date after which a different value is offered to the consumer.
  • a consumer may be offered a choice of value from a pool at a first stage.
  • a choice may be presented to a user at one or more stages or every stage of a multistage account.
  • no choice is offered to the user.
  • Machine learning may be applied to determine the value or pool of values offered at one or more stages of a multistage value account based on, for example, previous value selections by a user, use of the multistage value account identifier (e.g., redemption data), information submitted by a user, demographic data and/or any other information relevant to individualizing value to a user of a multistage value account.
  • the multistage value account identifier e.g., redemption data
  • information submitted by a user e.g., demographic data and/or any other information relevant to individualizing value to a user of a multistage value account.
  • Artificial intelligence may, for example, provide a multistage value system subscriber segmentation including groupings or patterns within a customer base of the subscriber.
  • the multistage value system subscriber may be offered choices of values to be offered to a user at one or more stages based on segmentation.
  • a multistage value system subscriber may be, for example, a game company, issuer, processor, acquirer, payment network, merchant, property owner (e.g., mall owner or strip mall owner) and/or an affiliate of a collection of merchant brands subscribing to, or operating, a multistage value system.
  • a multistage value system may according to at least some example embodiments be provided by a third party from a remote server.
  • a value offered to a user during one or more stages of a multistage value account may be the result of, for example, an online game or games (e.g., game scores).
  • a value offered during one or more stages may be random, for example, the result of a virtual scrath- off.
  • the system may be a merchant, cross-merchant, product and/or issuer centric system.
  • a merchant multistage value system may offer a user a value at each of multiple stages, the value usable or in exchange for, among other things, making purchases from the merchant, making purchases from different stores of the merchant and/or purchasing different preferred products from the merchant.
  • a cross-merchant multistage value system which may be provided by, for example, an issuer, and may offer a user a sequence of values corresponding to a sequence of purchases from different merchants.
  • a user may be provided values usable or in exchange for making a purchase at a first merchant at a first stage, at a second merchant at a second stage, a third merchant at a third stage or any combinations of merchants with or without repeats.
  • Stages may be related to, for example, non-competitive merchants, merchants familiar to one another, merchants selected according to machine learning and/or combinations thereof.
  • a multistage value account may include stages related to companies adverse to each other with the stage placement based on preferences of a multistage value system subscriber.
  • a user may be offered value for making a sequence of purchases of a particular product or a product from a family of products (e.g., for purchases of different flavors of a particular brand of ice cream).
  • a user may be offered a single value for making a purchase at a sequence of vendors, either additional to values provided at one or more individual stages of the sequence or otherwise.
  • a multistage value system may be used to induce user behavior. For example, a user may be offered value for travelling to specific geographic areas (e.g., malls, shopping districts, community revitalization projects) or different geographic locations (e.g., game vendor, amusement park locations, recreational facilities).
  • the multistage value system may be, for example, provided via a server of a merchant, acquirer, issuer, processor, payment network, third party service provider, remote facility, device provider, and/or any other entity.
  • a multistage value account identifier may be obtained in any manner value offers may be made.
  • a multistage value account identifier may be printed as a barcode on a receipt.
  • a user may obtain a generic identifier, submit the generic identifier and receive a multistage value account identifier.
  • a user may take a picture of a generic identifier in a newspaper or a screenshot of a web based advertisement, text or email the picture to a number provided in the newspaper or advertisement and receive a multistage account identifier in return from that number.
  • Persons having ordinary skill in the art in possession of this specification will understand that many different ways of providing an identifier are achievable and contemplated
  • a multistage value account may offer value based on a number of stages completed within a period of time (e.g., one month) and/or may change value based on the length of time between stage completion and/or may change the value based on the average length of time between completion of multiple stages and/or provide value based on a period of time in which all stages are completed.
  • a multistage value account identifier may be the same for all stages, different for groupings of stages or different for each stage.
  • FIG. 13 is an illustration of a process flow chart constructed in accordance with the principles of the present invention.
  • a server may receive a multistage value account identifier (e.g., a coupon identifier of a multistage coupon) and at least a portion of purchase transaction information (Step 1305).
  • the server may use the multistage value account identifier to access multistage account data associated with the identifier, obtain a current stage associated with the multistage value account and a stage threshold, and determine that the current stage is equal to or greater than the stage threshold (Step 1310).
  • the server may verify that the purchase qualifies a user of the multistage value account identifier to receive a value associated with the current stage based on the purchase transaction information (Step 1315).
  • the server may communicate a message indicating the earned value and eligibility for a loyalty card associated with the multistage value account based on the threshold (Step 1320). User information may be received by the server in response to the message (Step 1325).
  • a multi- stage account may be associated a number of stages that may be completed in any order.
  • one stage may provide a free coffee upon purchasing a dinner from Dew-Rain-Dew Restaurant, or in real-time, for example, upon ordering, such that the coffee is enjoyed as part of the experience.
  • a second stage of the multistage value may provide, for example, a free biscuit with breakfast, and a third stage may provide, for example, a free side with an entree at lunch.
  • the user may receive an all-stage completion reward, for example, a $10 gift card.
  • an employee of Dew-Rain-Dew Restaurant may accept a multistage value account identifier at any portion of the dinner meal.
  • the employee may scan a QR Code displayed on a phone of the customer.
  • the QR code may include the multistage value account identifier and may be uploaded to a remote server along with a merchant code indicating a purchase of a qualifying dinner.
  • the customer may be provided with an SMS number (e.g., a dynamic number that changes based on time) linked to such a remote server and associated with Dew-Rain-Dew restaurant, such that the multistage value account identifier may be texted to the remote server and the purchase of the dinner confirmed simultaneously.
  • the customer may not possess, and may be provided with, a multistage value account identifier for a new, unused account, for immediate or future use.
  • a merchant may permit back credit for previously purchased products (e.g., previous meals purchased from Dew-Rain-Dew Restaurant) and may provide a URL linked to a web GUI for managing a multistage value account.
  • the remote server may keep track of the stages and their completion regardless of the temporal order of completion. For example, the remote server may receive the multistage value account identifier and a merchant flag indicative of a stage, and update the multistage value account to reflect stage completion.
  • the remote server may communicate with merchant systems to affect application of the value, and if all-stage completion is achieved, provide value and/or notice to the multistage value account user.
  • the remote server may communicate with Dew-Rain-Dew Restaurant's register or billing server such that the free coffee is properly accounted for in the bill and if all-stage completion is achieved, provide notice to the multistage value account user (directly or through Dew-rain-Dew's employee).
  • FIG. 14 is an illustration of a process flow chart constructed in accordance with the principles of the present invention.
  • a user may scan a QR Code using a phone application (Step 1405).
  • a server may receive a multistage value account identifier from the phone application and access the multistage account data associated with the identifier (Step 1410).
  • the server may determine that the account is flagged for stage completion in any order and obtain stage completion data associated with the multistage value account (Step 1415).
  • the server may communicate the flag and data to the phone application (1420).
  • the phone application may display a list of stages showing which stages are complete, which stages are yet to be completed or a combination thereof, and may display stage requirements and values for uncompleted stages, and display a value associated with completion of all stages (1425). Accordingly, the user of the multistage value account may at any time check which stages are yet to be completed and verify the all stage completion reward, adding to the festive nature of the multistage value account.
  • software and/or hardware may be included in, for example, a point-of-sale (POS) terminal that identifies a barcode.
  • POS point-of-sale
  • a POS terminal may identify a QR code as being a QR code for a specific action, such as to authorize payment for a transaction.
  • the barcode such as a QR code, may identify routing information for that barcode.
  • the barcode as well as additional data such as basket level purchase data and other data associated with a transaction (e.g., tax amount) may be communicated to the routing identity in the barcode.
  • the barcode may identify routing information and include the additional data.
  • the barcode and/or associated data may be routed to the routing identity for further processing.
  • multiple barcodes may have been utilized with a purchase. For example, one or more coupon barcodes may have been used for discounts, a loyalty barcode may have been utilized for loyalty account identification, an installment barcode may identify a user's desire to pay for a purchase in installments, a points barcode may indicate that a purchase is to be paid with points (e.g., loyalty points) and a payment barcode may have been provided to complete payment for the transaction.
  • a barcode such as a QR code
  • a QR code may be encoded in a manner to convey a greater amount of data than a conventional QR code, using for example a high capacity QR format (e.g., 177 x 177), multi-level data, data compression, or defined combination function flags.
  • Mmultiple QR codes may be condensed into a single QR code.
  • a user may provide a POS terminal with a QR code that includes payment routing, loyalty, discount, installment, and/or points information, and/or other information.
  • a QR code may, for example, indicate combinations of QR codes to be communicated to a routing identity (e.g., a payment QR code with an installment QR code for a third party installment plan provider to define an installment plan).
  • each barcode may initiate a different process and information may be routed to those different processes (either in parallel or in serial).
  • the identification of the type of process e.g., coupon, loyalty, payment, installment, points
  • the system at the routing identity may receive, for example, all information, including all barcodes, and may determine the type of each barcode and initiate processes based off that determination.
  • the type of the barcode may be identified as a payment type.
  • the barcode may then include additional identifying information, such as the payment network for the payment account, the bank for the payment account, the user's account from that bank account, and additional discretionary data.
  • additional discretionary data may be a dynamic security code that changes with every use.
  • different barcodes may be provided by a device (e.g., a phone, watch, or battery powered card with a display) to make a payment at a store (e.g., via a point-of-sale system) and each of those barcodes may be associated to the same payment account from the same payment network and issuing bank with the difference being, at least in part, dynamic security data.
  • a device e.g., a phone, watch, or battery powered card with a display
  • a store e.g., via a point-of-sale system
  • each of those barcodes may be associated to the same payment account from the same payment network and issuing bank with the difference
  • magnetic stripe information could be, for example, represented as a barcode.
  • a dynamic magnetic stripe security code may be provided as part of the dynamic magnetic stripe data. Such data may be communicated to a point-of-sale terminal, identified and routed to that identified process, and the identified process may replace the barcode with magnetic stripe data, or generate magnetic stripe data, and may communicate this information to a payment network and perform an authorization process for that magnetic stripe data with a payment network.
  • a token may be utilized, such as a token issued by a token issuing entity, as the data for payment authorization.
  • a message may be sent back to the point-of-sale terminal that causes the transaction to be completed.
  • This can be done in many ways. For example, an amount of value may be stored in escrow and the point-of-sale terminal may be provided with indication that stored value is being utilized for the purchase amount and, after the transaction completes, the merchant's account may be deposited with the amount of the purchase. As such, the merchant may get access to funds quickly after a purchase transaction occurs.
  • merchants may enter into contracts to accept the payment network's issuers barcodes for various types of payment (e.g., debit, credit, pre-paid) and transactions may be authorized and merchants paid within these terms.
  • types of payment e.g., debit, credit, pre-paid
  • Bank issuers may include their own wallets that run their own cards as dynamic barcodes, such as dynamic QR codes.
  • Phone manufactures may find such features difficult to block as such features do not include the use of secure hardware on the devices.
  • the barcodes may be generated locally using local algorithms (e.g., stored in white box crypto approaches on the phone applications) or may be retried from a third party (e.g., retrieved and stored from a secure cloud). Such barcodes may be retrieved in batches (e.g., of 5 or more, 10 or more, 100 or more, etc). Such barcodes may be deleted after use so that the information is not retained on the device in any form.
  • a multi-issuer and multi-network wallet may be provided that permits a consumer to load in dynamic barcodes from various issuers.
  • a user may be able to enter in his/her payment information either manually or via a phone (with an OCR component of an application reading information from the picture of the card).
  • a token service may then be called to obtain an eligible payment token for the card. This token may be converted into a static or dynamic QR code.
  • a Dynamic Payment Barcode e.g., as a Dynamic Payment Barcode
  • the dynamic payment process may check to determine if other barcodes are utilized (e.g., a coupon barcode, loyalty barcode, etc.) and all barcode may be processed in order to properly complete a transaction.
  • the barcode may identify the network and the appropriate information for that network may be communicated to obtain authorization of the payment information.
  • a decline may be received from the network and cause a decline communication to be sent to the point-of sale.
  • An approval may be received from the network and cause an approval communication to be sent to the point of sale.
  • Additional information may be sent to the network, such as additional information to assist with other processes such as fraud detection and marketing insight evaluation.
  • a payment card or other device such as a payment phone or watch, can interact with a point-of-sale terminal to complete a transaction.
  • Multiple stages of communications from the payment device to the payment terminal and from the payment terminal to the payment device can be provided so that each device or process can identify itself to each other, securely confirm the other identity is authorized to conduct a transaction, and provided information for the authorization of a payment transaction.
  • the point-of-sale terminal may route such communications to/from a merchant processor which may route parts of the communication to/from a payment network process, which may route part of the communications to/from an issuing processor that issued the payment device to the end consumer.
  • the transaction may be communication between the payment device and point-of-sale terminal, for example, a contact chip connection, a contact or wireless magnetic stripe connection, a contactless connection, or through a visible connection such as a single-stage or multipl-stage barcode or QR code.
  • a multiple-stage barcode may be a barcode that changes the information displayed throughout a payment transaction process so that multiple different types of information are displayed at different times over the same display area.
  • This information may include, the amount authorized, additional monetary amounts, the country code of the terminal, the terminal verification results, the transaction currency code, the transaction data, the transaction type, the data authentication code, the iCC dynamic number, the CVM results, the transaction time, merchant custom data, transaction date, tvr, unpredictable number, whether the transaction was authorized or declined, or any type of data retrievable by the payment card.
  • a payment card may be battery-powered or non- battery powered and may include buttons to permit a consumer to select different payment accounts (e.g., debit, credit, pre-paid), payment options (e.g., pay with points, pay with equal monthly payments such as 3, 6, 9, 12, 15, 18, 21, 24, 27, 30, 36, 39, 42, 45, or 48 monthly payments, or other payment features (e.g., a password- entry system where a correct password is needed to use the card to complete a purchase).
  • payment accounts e.g., debit, credit, pre-paid
  • payment options e.g., pay with points, pay with equal monthly payments such as 3, 6, 9, 12, 15, 18, 21, 24, 27, 30, 36, 39, 42, 45, or 48 monthly payments
  • other payment features e.g., a password- entry system where a correct password is needed to use the card to complete a purchase.
  • the payment devices may include multiple processors - such as a general processor for managing the general operation of the device and a payments processor or secure memory element for managing all or part of the payment data and payment process of the device.
  • processors such as a general processor for managing the general operation of the device and a payments processor or secure memory element for managing all or part of the payment data and payment process of the device.
  • Data not associated with the direct authorization of a payment may be copied from information requested from the payment device and stored and utilized for non-payment or payment features.
  • a card may have a display such as a pixelated display operable of displaying a cardholders payment network logo, cardholder name, payment account number, payment expiration date, payment security code for online transactions (e.g., CVV2, CVC2), card name, and other pieces of information.
  • a display such as a pixelated display operable of displaying a cardholders payment network logo, cardholder name, payment account number, payment expiration date, payment security code for online transactions (e.g., CVV2, CVC2), card name, and other pieces of information.
  • Messages associated with a particular time and/or date may be pre-stored. For example, messages associated with an anniversary date of the issuance of the card, consumer birthday information, country holidays, religious events, or any notification or message associated with a particular time or date. For example, a message wishing the consumer a happy birthday and providing the consumer with a QR code coupon for a certain amount in value may be displayed based on a date received during a payment transaction (and, for example, a clock in the payment device that updates the stored date as time passes).
  • a birthday event may trigger a feature such as a game feature where a consumer gets to pick a gift box from a number of gift boxes where each or one ore of the gift boxes has a different amount or type of value stored in it.
  • a marketing campaign may be provided where on your birthday you have the chance to win a statement credit for your payment card bill in different amounts based on, for example, an instant no- purchase necessary sweepstakes where on the cardholders birthday the cardholder is provided instant statement credit value based on different odds of receiving different amounts of value.
  • Pre-stored messages based on time could be provided so that a different message is released at a particular time (e.g., 9am EST) every day. Date-based messages could include for example, new years, Christmas, Ramadan, each day of hannakah, memorial day, independence day, election day, etc.
  • Payment devices such as payment cards, may include, for example, one or more displays, light emitting diodes, programmable magnetic stripes that can change the magnetic stripe data on the magnetic stripe, programmable EMV chips, programamble contactless chips, cellular chips and antennas for downloading data from a remote source, manual interfaces, sound interfaces, etc
  • a dynamic security code may be changed based on time and/or date information received from the payment device during an authorization transaction on a two-way authorization process (e.g., via an EMV or contactless transaction).
  • the dynamic security code may provide a dynamic in-stripe security code (e.g., CVC1/CV1) and on-line security code (e.g., CVC2/CVV2). They may be the same or different security codes based on time and/or date or other information received and multiple types of information received (e.g., a different code may be provided based on time and country information received during a payment transaction).
  • Pre-stored messages may be provided based on any information received such as, for example, country code.
  • a welcome message may be provided after a consumer makes a payment transaction in a new country that welcomes the user to the country and provides the consumer with payment information (e.g., exchange rates) based on that country.
  • payment information e.g., exchange rates
  • a card may display information on the transaction (e.g., amount of the transaction) in both the local and foreign currency by using information received and/or logic on the card.
  • Transaction applets may be provided that changes the account or payment option information based on what was received during the transaction. For example, if a US card account is utilized in Spain then the card may change the account to a Spanish account for future transactions (unless otherwise directed by the cardholder). In doing so, the payment device can receive information and change the way the payment devices operated based on the received information.
  • Any information could enable a new account (e.g., debit credit) or payment option (e.g., EMI, pay with points) for the current or a future transaction.
  • a card can terminate a transaction based on information received and start a subsequent transaction (e.g., by having the cardholder remove and replace the card in a chip contact reader or reinstitute a new contactless transaction, etc.
  • Payment terminals can be constructed to reinstitute transactions automatically if a transaction fails.
  • Example types of information receivable to cause modification of an applet, or by an applet may include, for example:
  • Perso Data Encryption may be sent over a transmission link (e.g., cell network, Bluetooth, NFC, etc.).
  • a perso data block may have a unique session identifier preprogrammed into a secure element (SE) which may be used as part of an decryption process.
  • SE secure element
  • Data may be encrypted at multiple levels.
  • a two level embodiment may include transmission link encryption.
  • An entire block of perso data may be encrypted (e.g., 3DES, AES, etc.) during transmission.
  • This block may be decrypted by, for example, a general purpose processor (GP).
  • the GP may use a unique Session Identifier to request the transmission decryption key from the Secure Element.
  • Such a two level embodiment may further include encryption of sensitive perso data (personal data of a cardholder) - sensitive perso data such as UDKs may be encrypted such that they will never be in the clear.
  • This information may be sent encrypted to the SE (such as a secure element chip) and may be decrypted inside the Secure Element. This decryption process may be performed by an applet installed on the SE.
  • Cards may be preloaded with sets of keys in the SE that are associated with: Transmission Link Key - This key may be utilized by the GP to decrypt the entire perso data block that was received.
  • the GP may provide the unique session identifier provided with the perso data Block to the SE such that the appropriate key can be provided.
  • Multiple unique transmission keys (each associated with a unique Session Identifier) may be preloaded such that multiple perso upgrades can be performed over the life of the card. This process may be protected from attacks by, for example, only allowing three attempts to request the transmission link key and if the proper unique session identifier is not provided within three attempts, the process may be blocked going forward.
  • Sensitive Perso Data Key - This key may be utilized by the SE to decrypt sensitive perso data.
  • the unique session identifier may be provided to the SE to be able identify the proper preloaded keys to decrypt the sensitive perso data.
  • Multiple unique sensitive perso data keys (each associated with a unique Session Identifier) may be preloaded such that multiple perso upgrades may be performed over the life of a card. This process may be protected from attacks by only allowing three attempts to provide a unique session identifier and if the proper unique session identifier is not provided within three attempts, the process will be blocked going forward.
  • Preloaded Perso Data Acording to some example embodiments, preloading either multiple entire sets of perso data or multiple partial sets of perso data (which may be unique to this card) which may be triggered to be used by sending a signal to the card over a transmission link (e.g., cell network, Bluetooth, NFC, etc.) to change account information.
  • a transmission link e.g., cell network, Bluetooth, NFC, etc.
  • Partial Sets of Perso Data In order to minimize the amount of data preloaded, only the unique data associated with an account upgrade (PAN, UDKs, certificates, etc.) may be preloaded. Multiple partial sets of Perso Data which may, for example, include changes based on an update to PAN sequence number only or entirely different PANs may be preloaded on the SE. Each of the Partial Sets of Perso Data may be associated with a unique account identifier programmed into the SE. When a change in account is deemed necessary a signal may be sent to the card including the unique account identifier associated with the next set of account data. This unique account identifier may be sent to the SE and if it matches the next account data the card may begin using that Account information. This process may be protected from attacks by only allowing three attempts to provide a unique account identifier and if the proper unique account identifier is not provided within three attempts, the process may be blocked going forward.
  • PAN unique data associated with an account upgrade
  • UDKs, certificates, etc. may be
  • a slider may be used to select different features instead of, for example, a button.
  • a slider may have any states such as for example, two states, three states, four states, or more than four states.
  • a slider may have multiple stopping positions and each stopping position may be associated with a different account, payment option, or other feature.
  • a slider may not be associated with a supplemental visual indicator (e.g., a light emitting diode and/or display) as the slider itself may be the visual indicator.
  • a slider oriented card may be have a reduced cost.
  • a slider oriented card may have, for example, no battery and may not be battery powered.
  • a slider may provide a control signal to a processor (e.g., a contact payments chip such as an EMV chip and/or a contactless chip). Accordingly, a card may be placed in a contact EMV payment card reader and the reader may deliver power to the EMV chip, and associated electronics.
  • Firmware in a payments chip may utilize the control signal(s) from the slider to determine the position of the slider.
  • the firmware may utilize a different option and/or payment account and/or feature for the card when it is used in a payment card reader.
  • a cardholder may slide a slider switch (or another stationary switch that can mechanically retain a state such as a lever switch or a push-button switch) to a desired option (e.g., credit account, debit account, pay in 6-month equated monthly installment (EMI, 12-month EMI, 18-month EMI, 24 month EMI, 30 month MEI, pay with rewards, etc.).
  • Such a non battery powered card may include, for example, a static magnetic stripe.
  • the static magnetic stripe may, for example, have a payment card account number of the highest interchange payment card account on the card (e.g., or the lowest interchange payment card account on the card).
  • a single EMV chip may include contact (e.g., for contactless readers) and contactless (e.g., for contactless readers).
  • a contactless RF field may, for example, power the chip such that firmware associated with a slider, or other stationary position switch, may be retrieved.
  • a battery may be included, for example, to assist with certain types of payments (e.g., contactless payments) and that does not assist with other types of payments (e.g., contact payments).
  • contact reader power may be utilized to power an electronics package to run slider-selected options when in the contact reader (e.g., EMV reader) and a battery may be utilized to power an electronics package to run slider-selected options when in a contactless reader (e.g., EMV contactless reader).
  • a recharging circuit e.g., a recharging chip
  • a contact reader e.g., an EMV contact payment reader
  • a contactless reader e.g., an EMV contactless payment reader
  • FIG. 5 shows card segment 1500 that may include aperture 1501, slider base 1502, and slider handle 1502.
  • slider base 1502 may be larger than aperture 1501 and may be in a cavity so slider base 1502 may slide.
  • Conductive contacts may couple with conductive wires on an electronic circuit board of an electronics package when slider base 1502 is moved into different positions by slider handle 1503.
  • an aperture may be an aperture in a plastic skin of a card and may be opened via an etching process such as a laser etching process.
  • a circuit board may have a material (e.g., gold) that reflects a laser so that the circuit board is not damaged during etching.
  • a slider switch may be coupled to a circuit board and the card may be laminated. Lamination may then be removed using a process such as, for example, a process that removes laminate over the switch.
  • Slider handle 1503 may be an impression instead of, for example, an extrusion. In doing so, a slider switch handle may not extend above the surface of a card. Alternatively, for example, a slider switch handle may extend above the surface of a card.
  • Printed indicia may be printed on the card to indicate the states of slider switch base 1502. Any number of states may be selected from one or more slider switches.
  • Card 1510 may be provided and may include a slider switch to select between two states (e.g., a credit account for one state and a debit account for another state).
  • Card 1510 may include, for example, a printed account number for any state of a slider switch. Accordingly, card 1510 may include a printed debit account number and a printed credit account number.
  • each credit account, or payment option/feature may have a different printed card not present security code (e.g., online security code such as a CVC or CVV) and such online security codes may be, for example, 3 or 4 digits in length.
  • Such online security codes may be printed on the same side of a card as the associated payment number/option or may be printed on a different side.
  • a printed label may be located next to each online code to indicate the option/account/feature associated with the online security code.
  • Card 1530 may be included and may have a slider switch associated with a payment card and a payment card option (e.g., a credit account and an installment option associated with that credit account). Selecting an installment option may, for example, provide in a payment data message (e.g., an EMV, contactless, and/or magnetic stripe data) a flag associated with the selected option. Accordingly, an EMI option may be selected and the credit card account associated with the card may be communicated to a payment card reader. A flag associated with the selected payment option (e.g., EMI) may be communicated. This flag may be retrieved, for example, after authorization of the underlying payment account (e.g., credit card account).
  • a payment data message e.g., an EMV, contactless, and/or magnetic stripe data
  • the flag may be recognized as being associated with a particular option and then a process associated with the option may be initiated (e.g., an installment option).
  • a cardholder may change the option associated with a state of a button (e.g., a slider switch) using a different device (e.g., a mobile telephonic device or a portable or stationary computer on a website). Accordingly, a cardholder may change an option from a 6 month EMI to a 12 month EMI to a pay with points option.
  • the flag, for example, communicated by the card may stay the same regardless of the option selected by a consumer, but after the flag is received, a processing system may retrieve (e.g., from a remote storage facility) the option associated with that flag that a cardholder selected (e.g., on the user's mobile phone).
  • Card 1550 may include, for example, card structure 1551 which may be for example, a plastic such as a laminated plastic.
  • Card 1550 may include circuit board 1560 which may be a flexible circuit board and may be, for example, less than six thousandths of an inch in thickness (e.g., less than four thousandths of an inch in thickness.
  • Circuit board 1560 may include contact payment reader contacts 1552 and may include, for example, 6 contacts, 8 contacts, or any amount of contacts.
  • circuit board 1560 may be laminated and embedded in structure 1551 and contacts 1552 may be lasered out and then filled up to the surface of the laminate with a material (e.g., a conductive material such as a silver).
  • Processor 1553 as well as additional circuitry may be coupled to processor 1553 or other components of circuit board 1560.
  • Slider switch 1553 may be provided on circuit board 1560 and coupled to processor 1553 or any component of card 1561.
  • a static (or electronically programmable magnetic stripe communications device) may be included in card 1550 as well as a RFID antenna and associated processing chip.
  • Such an RFID antenna may be independent from circuit board 1560 and may have an independent chip and may be programmed with payments data independently from a chip associated with contacts 1552.
  • Contacts 1552 and an RFID antenna may share the same processor and/or secure storage element for secure payments data.
  • FIG. 16 shows a card with an orientation of detectors 1626 and dynamic magnetic stripe communication device 1630, whereby one or more detectors 1602-1616 and dynamic magnetic stripe communication device 1630 may be, for example, arranged along a length of card 1600.
  • Detectors 1602-1616 may be provided, for example, as conductive pads using, for example, an additive technique, whereby patterns of a conductive element (e.g., copper) may be applied to a PCB substrate according to a patterning mask definition layer. Detectors 1602-1616 may be provided, for example, as conductive pads using, for example, a subtractive technique whereby patterns of a conductive element (e.g., copper) may be removed from a pre-plated PCB substrate according to an etching mask definition layer. Other non-PCB fabrication techniques may be used to implement conductive pads 1602-1616 as may be required by a particular application.
  • an additive technique whereby patterns of a conductive element (e.g., copper) may be applied to a PCB substrate according to a patterning mask definition layer.
  • Detectors 1602-1616 may be provided, for example, as conductive pads using, for example, a subtractive technique whereby patterns of a conductive element (e.g., copper) may be removed from
  • Processor 1618, conductive pads 1602-1616, processor 1618, dynamic magnetic stripe communication device 1630, inductive sensor circuitry 1628 and multiple sensor algorithm 1632 may be combined to provide a multiple sensor detection system.
  • each of conductive pads 1602-1616 may be utilized by processor 1618 as capacitive sensing pads.
  • Processor 1618 may include the functionality to control and determine when an object is in the proximity of one or more conductive pads via a capacitive sensing technique.
  • Dynamic magnetic stripe communications device 1630 and inductive sensor circuitry 1628 may be utilized by processor 1618 as an inductive sensing device.
  • a processor may include the functionality to independently utilize multiple portions of dynamic magnetic stripe communications device 1630 and determine when an object is in the proximity of one or more of the portions via an inductive sensing technique.
  • FIG. 49 shows capacitive detection circuitry 1700.
  • a conductive pad may be utilized, for example, as a conductor of a capacitive device within a resistor/capacitor (RC) circuit to determine the capacitance of a conductive pad and determine whether the capacitance is below, equal to, or above one or more predetermined thresholds.
  • RC resistor/capacitor
  • a conductive pad may, for example, form a portion of a capacitive element, such that plate 1716 of capacitive element 1714 may be implemented by a conductive pad and the second plate of capacitive element 1714 may be implemented by element 1710.
  • Element 1710 may represent, for example, the device or object whose proximity or contact is sought to be detected.
  • the capacitance magnitude of capacitive element 1714 may exhibit, for example, an inversely proportional relationship to the distance separation between plate 316 and device 310.
  • the capacitance magnitude of capacitive element 1714 may be relatively low when the corresponding distance between plate 316 and device 1710 may be relatively large.
  • the capacitance magnitude of capacitive element 1714 may be relatively large, for example, when the corresponding distance between plate 1716 and device 1710 is relatively small.
  • Capacitive detection may be accomplished, for example, via circuit 1700 of FIG. 49. Through a sequence of charging and discharging events, an average capacitance magnitude for capacitive element 1714 may be determined over time. In so doing, the spatial relationship (e.g., the separation distance) between plate 1716 and device 1710 may be determined.
  • Charge sequence 1750 may be invoked, such that charge circuit 1704 may be activated at time Tl, while discharge circuit 1706 may remain deactivated. Accordingly, for example, current may flow through resistive component 1708. In doing so, for example, an electrostatic field may be generated that may be associated with capacitive component 1714.
  • Discharge sequence 1760 may be invoked, such that discharge circuit 1706 may be activated at time T2, while charge circuit 1704 may remain deactivated.
  • the electric field associated with capacitive element 1714 may be allowed to discharge through resistive component 1708 to a reference potential (e.g., ground potential).
  • the charge and discharge times may be utilized to calculate a capacitance magnitude that may be exhibited by capacitive element 1714.
  • a capacitance magnitude For example, given that the magnitude of voltage, VI, may be equal to approximately 63% of the magnitude of voltage, VS, then a first relationship may be defined by equation (1) as:
  • TCHARGE R 1708 *C1, (1) where R 1708 the resistance magnitude of resistive element 1708 and Cl is proportional to a capacitance magnitude of a capacitive element (e.g., capacitive element 1714).
  • the capacitance magnitudes, C 1 and C 2 may then be calculated from equations (1) and (2) and averaged to determine an average capacitance magnitude that is exhibited by capacitive element 1714.
  • circuits 1704 and 1706 may be activated and deactivated by controller 1720. Accordingly, for example, controller 1720 may control when the charge and discharge events occur.
  • controller 1720 may adjust a frequency at which circuits 1704 and 1706 may be activated and/or deactivated, thereby adjusting a sampling rate at which the capacitance magnitudes, C 1 and C 2 , may be measured. In so doing, a sampling rate (e.g., a lower sampling rate) may be selected in order to select a power consumption rate of a card (e.g., a lower power consumption rate). Controller 1720 may, for example, store capacitance magnitude measurements within memory 1718. Accordingly, for example, multiple capacitance magnitudes may be stored for subsequent access by controller 1720.
  • a conductive pad may be utilized, for example, as a conductor of a capacitive device within a resistor/capacitor (RC) circuit to determine the capacitance of a conductive pad and determine whether the capacitance is below, equal to, or above one or more predetermined thresholds.
  • RC resistor/capacitor
  • a series of charge and discharge sequences for pads 1602-1616 may be executed by processor 1618 to determine, for example, a relative capacitance magnitude that is exhibited by each of pads 1602-1616.
  • a series of charge and discharge sequences for each of pads 1602-1616 may be executed by processor 1618, for example, in order to obtain a capacitance characteristic for each of pads 1602-1616 over time.
  • a determination may be made, for example, as to when pads 1602-1616 are in a proximity, or touch, relationship with a device whose presence is to be detected. For example, a sequential change (e.g., increase) in the relative capacitance magnitudes of pads 1602-1608, respectively, and/or pads 1616-1610, respectively, may be detected and a determination may be made that a device is moving substantially in direction 1622 relative to card 1600.
  • a sequential change (e.g., increase) in the relative capacitance magnitudes of detectors 1610-1616, respectively, and/or 1608-1602, respectively, may be detected, for example, and a determination may be made that a device is moving substantially in direction 1624 relative to card 1600.
  • processor 1618 may activate inductive sensor circuitry 1628 in order to determine if the object is inductively detectable.
  • FIG. 50 shows inductive detection circuitry 1800.
  • inductive detection circuitry 400 may include, for example, coil portions 1805-1815, amplification and detection determination devices 1820 and 1830, oscillator 1825 and processor 1835.
  • Coil portions 1805-1815 may be portions of a coil, for example, portions of a coil in a dynamic magnetic stripe communications device.
  • Coil portion 1810 may be, for example, a central portion of a coil in a dynamic magnetic stripe communications device, and may be connected across oscillator 1825, or may be one or more separate coils.
  • Oscillator 1825 may be, for example, an electronic circuit that produces a repetitive, oscillating electrical signal (e.g., an alternating current and/or voltage) and/or may be a signal from an output of a port on processor 1835.
  • a control signal CTRL may be communicated to oscillator 1825 (e.g., by processor 1835) to initiate application of the electrical signal to coil portion 1810.
  • a time- varying magnetic field may be generated by coil portion 1810 due to the signal. The time varying magnetic field may induce repetitive, oscillating electrical signals in each of coil potions 1805 and 1815.
  • Coil portions 1805 and 1815 may be, for example, side portions of a coil in a dynamic magnetic stripe communications device. Although FIG. 18 shows coil portions 1805 and 1815 adjacent to coil portion 1810, example embodiments are not so limited. Coil portions 1805-1815 may be, for example, separated by other coil portions (not shown).
  • Coil portion 1805 may be connected to oscillator 1825 (e.g., a high frequency oscillator), and connected across amplification and detection determination device 1820.
  • Amplification and detection determination device 1820 may receive the oscillating signal induced in coil portion 1805 by coil portion 1810, and output a signal OUT1 to processor 1835.
  • Coil portion 1815 may be connected to oscillator 1825, and connected across amplification and detection determination device 1830.
  • Amplification and detection determination device 1830 may receive the oscillating signal induced in coil portion 1815 by coil portion 1810, and output a signal OUT2 to processor 1835.
  • Signals OUT1 and OUT2 may indicate whether or not signals induced in coil portions 405 and/or 1815 are less than, equal to or greater than a threshold signal value.
  • the threshold signal value may be based on the magnitude of the signals induced in coil portions 1805 and 1815 when coil portions 1805 and 1815 are adjacent to an object (e.g., a read-head of a card reader), and when coil portions 1805 and 1815 are not adjacent to an object.
  • an object e.g., a read-head of a card reader
  • inductive detection may be implemented by determining coupling responses in coil end sections and setting response threshold values.
  • an oscillating signal may be applied to a center portion of a coil in dynamic magnetic stripe communications device 1630 by processor 1618 via inductive sensor circuitry 1628.
  • a coupling response in the coil end sections may be determined both when an object is within proximity of card 1600 and when no object is within proximity of card 1600.
  • the coupling response may be determined by, for example, measuring a current and/or voltage across the end coil sections. Based on a difference between the coupling responses, a threshold value may be determined.
  • Multiple sensor algorithm 1632 may utilize the threshold value to determine whether or not an object is detected.
  • multiple threshold values may be determined in order to discriminate between multiple different objects.
  • multiple different objects may be passed in proximity to dynamic magnetic stripe communications device 1630 to determine a coupling response of the end coil sections in the presence of each of the objects.
  • the coupling response may be determined by, for example, measuring a current and/or voltage across the end coil sections in the presence of each object.
  • One or more threshold signal values may be determined based on the coupling responses.
  • a human finger, a skimmer, a first type of read-head and a second type of read-head may be passed within proximity of dynamic magnetic stripe communications device 1630.
  • a change in coupling between the center and end sections of the coil in magnetic stripe communications device 1630 for each object may be determined.
  • One or more thresholds may be set such that during normal operation processor 1618 will activate dynamic magnetic stripe communications device 1630 to communicate data in the presence of the first and second type of read-head, but not in the presence of the skimmer or human finger.
  • three separate threshold values may be set.
  • a determination may be made, for example, as to when the coil end sections are in a proximity, or touch, relationship with a device whose presence is to be detected.
  • Inductive sensor circuitry 1620 and dynamic magnetic stripe communications device 1630 may be used in conjunction with, for example, one or more pads 1602- 1616 to determine that a device (e.g., a read-head housing of a magnetic stripe reader) is in close proximity, or touching, one or more of pads 1602-1616.
  • Processor 1618 may, for example, utilize multiple sensor algorithm 1632 to detect a device moving with respect to card 1600.
  • multiple sensor algorithm 1632 may analyze a capacitance change in one or more conductive pads to determine that a device is moving in relation to pads 1602-1616.
  • processor 1618 may, for example, apply an oscillating signal to a center portion of dynamic magnetic stripe communication device 1630 and detect a coupling response of side portions of dynamic magnetic stripe communication device 1630. If a coupling response indicates that (e.g., inductive detection) an object is detected, processor 1618 may communicate with the detected device via dynamic magnetic stripe communications device 1628.
  • FIG. 19 shows inductive detection circuitry 1900.
  • inductive detection circuitry 1900 may include, for example, coils 1905-1915, amplification and detection determination devices 1920 and 1930, oscillator 1925 and processor 1935.
  • Coil 1910 may be, for example, a coil of a dynamic magnetic stripe communications device and/or a coil separate from the dynamic magnetic stripe communications device. Coil 1910 may be connected across oscillator 1925.
  • Oscillator 1925 may be, for example, an electronic circuit that produces a repetitive, oscillating electrical signal (e.g., an alternating current and/or voltage).
  • Oscillator 1925 may be, for example, a processor (e.g., a signal may be output from a port of a processor).
  • a control signal CTRL may be communicated to oscillator 1925 (e.g., by processor 1935) to initiate application of the electrical signal to coil 1910.
  • a time-varying magnetic field may be generated by coil 1910 due to the signal. The time varying magnetic field may generate repetitive, oscillating electrical signals in each of coils 1905 and 1915.
  • Coils 1905 and 1915 may be, for example, detection coils on opposite ends of a card.
  • coils 1905 and 1915 may be adjacent to capacitive sensors at ends of a card.
  • Coil 1905 may be connected across amplification and detection determination device 1920.
  • Amplification and detection determination device 1920 may receive the oscillating signal induced in coil 1905 by coil 1910, and output a signal OUT1 to processor 1935.
  • Coil 1915 may be connected across amplification and detection determination device 1930.
  • Amplification and detection determination device 1930 may receive the oscillating signal induced in coil 1915 by coil 1910, and output a signal OUT2 to processor 1935.
  • Signals OUT1 and OUT2 may indicate whether or not signals induced in coil portions 1905 and/or 1915 are less than, equal to or greater than a threshold signal value indicating whether or not an object is inductively detected.
  • the threshold signal value may be based on the magnitude of a signal induced in coil 1905 and/or coil 1915 when coil 1905 and/or coil 1915 is adjacent to an object (e.g., a read-head of a card reader), and the magnitude of a signal when coil 1905 and 1915 are not adjacent to an object.
  • an object e.g., a read-head of a card reader
  • FIG. 20 shows a card that is in proximity to an object 2002.
  • Card 2015 may be in proximity to object 602 such that a distance between conductive pad 2006 and object 2002 is less than a distance between conductive pad 608 and object 2002.
  • a capacitance magnitude that may be associated with conductive pad 2006 may be, for example, greater than a capacitance magnitude that may be associated with conductive pad 2008.
  • capacitance values may be relative to each pad and that a capacitance magnitude of a proximate pad may be equal to or less than a pad that is farther away from an object depending on, for example, manufacturing variation.
  • Such pads may be in any case characterized such that the detected capacitances may be used to determine which pad is closer to an object.
  • a processor that may be monitoring the capacitance magnitudes of conductive pads 2006 and 2008 may determine, for example, that object 2002 is close to conductive pad 2006. Based on the determination, the processor may cause a time-varying signal to be applied to coil 2011, and may monitor coils 2010 and 2009 to determine a property (e.g., relative conductivity) of object 2002 (e.g., a read-head of a magnetic stripe reader).
  • a property e.g., relative conductivity
  • Card 2025 may be in proximity to a device (e.g., read-head 2012) that may have moved from position 2020 such that a distance between conductive pad 2018 and device 2012 may be slightly greater than a distance between conductive pad 2016 and device 2012.
  • a capacitance magnitude that may be associated with conductive pad 2016 may be, for example, slightly greater than a capacitance magnitude that may be associated with conductive pad 2018.
  • a processor that may be monitoring the capacitance magnitudes of conductive pads 2016 and 2018 may determine that a device may be travelling in direction 2014. Further, a processor may determine that a device is slightly closer to conductive pad 2016 than to conductive pad 2018.
  • the processor may initiate inductive detection when device 2012 is at, for example, position 2020, by applying a time-varying signal to coil 2021, and may terminate the signal upon detecting device 2012 via coil 2019 and/or 2017.
  • Card 2035 may be in proximity to a device (e.g., read-head 2022) that may have moved from position 2032 to 2034. Accordingly, for example, a capacitance magnitude that may be associated with conductive pad 2028 may be slightly greater than a capacitance magnitude that may be associated with conductive pad 2026. In so doing, for example, a processor that may be monitoring the capacitance magnitudes of conductive pads 2026 and 2028 may determine that a device may be travelling in direction 2024. Further, a processor may determine that a device is slightly closer to conductive pad 2028 than to conductive pad 2026.
  • the processor may initiate inductive detection when device 2022 is at, for example, position 2034 by applying a time-varying signal to coil 2033, and may terminate the signal upon detecting device 2022 via coil 2031 and/or 2032, and/or within a period of time.
  • Device 2022 may move from position 2034 to position 2036. Accordingly, for example, a capacitance magnitude that may be associated with conductive pad 2030, for example, may be slightly greater than a capacitance magnitude that may be associated with conductive pad 2028. In so doing, for example, a processor that may be monitoring the capacitance magnitudes of conductive pads 2030 and 2028 may determine that a device may be travelling in direction 2024.
  • a processor may determine, for example, that a device is first located closest to conductive pad 2026, the device is then located closest to conductive pad 2028, and the device is then located closest to conductive pad 2030 in succession by detecting, for example, that a capacitance magnitude of conductive pad 626 changes (e.g., increases), followed by a capacitance change (e.g., increase) of conductive pad 2028, and then followed by a capacitance change (e.g., increase) of conductive pad 2030, respectively.
  • a capacitance magnitude of conductive pad 626 changes (e.g., increases) followed by a capacitance change (e.g., increase) of conductive pad 2028, and then followed by a capacitance change (e.g., increase) of conductive pad 2030, respectively.
  • a processor may activate one or more electromagnetic field generators to initiate a communications sequence with, for example, read-head 2022.
  • Each of the capacitance changes, the direction of movement and the inductive sensing may be used to determine that card 2035 is moving with respect to a read-head in an expected fashion, for example, a swipe through a card reader.
  • a communication sequence may be initiated upon card 2035 determining that an expected sequence of events has occurred.
  • Sequences and relative timings of events may be known for various other types of readers (e.g., dip and/or motorized readers). Accordingly, data communication and data security may be improved. Persons of ordinary skill in the art will appreciate that read- head detection may occur in a similar fashion for movement in a direction opposite to direction 2024.
  • a sequential capacitance change in conductive pads 2026-2030, respectively, may not occur.
  • a speed at which a device (e.g., read-head 2022) travels in direction 2024 relative to card 2035 may cause a processor to detect a capacitance change, for example, in conductive pad 2026 followed by a capacitance change in conductive pad 2030, but a capacitance change in conductive pad 2028 may not be detected.
  • a processor may execute a detection algorithm with an awareness of capacitance changes in non-adjacent conductive pads (e.g., conductive pads separated by one or more other conductive pads).
  • a processor may nevertheless determine that a device is moving in proximity to a card and may activate a communications device in response to such a detection.
  • a processor may, for example, detect devices moving at increased speeds (e.g., twice an average swipe speed) without sacrificing detection accuracy.
  • a processor may measure a magnitude of capacitance changes in conductive pads 2026-2030 that is not, for example, consistent with movement of a device in direction 2024. For example, a processor may first measure a capacitance magnitude associated with conductive pad 2026 that may be larger than a capacitance magnitude of either of conductive pads 2028 and 2030.
  • a processor may next measure a capacitance magnitude associated with conductive pad 2030 that may be larger than a capacitance magnitude of either of conductive pads 2026 and 2028.
  • a processor may next measure a capacitance magnitude associated with conductive pad 2028 that may be larger than a capacitance magnitude of either of conductive pads 2026 and 2030.
  • movement of a device in direction 2024 may be considered to be inconsistent with such a capacitance characteristic, since sequential capacitance magnitude increases may not be detected in conductive pads 2026, 2028, and 2030, respectively.
  • a processor executing a multiple sensor algorithm may have an awareness that detected capacitance increases may be inconsistent with an actual direction of movement of a device.
  • a processor may determine that a device is in proximity to card 2035, is not moving in direction 624, and may not, for example, activate a communications device in response to such a detection.
  • FIG. 21 shows a detection method flow diagram.
  • a sensor state change e.g., an increased capacitance
  • a second type of sensor may be activated in response to the sensor state change (e.g., as in step 2112).
  • a state of the second type of sensor e.g., an inductive detection of a conductive object
  • a communication sequence may be activated (e.g., as in step 2114) and/or the second type of sensor may be deactivated.
  • a card may be fully operational (e.g., as in step 2121 of sequence 2120), whereby a communication sequence may be activated after a device is detected to be in proximity, or touching, the card.
  • a state change of a first type of sensor e.g., an increased capacitance
  • a low-power mode of a card may be activated based on the state change detection (e.g., as in step 2123).
  • FIG. 22 shows inductive detection circuitry 2200.
  • Inductive detection circuitry 2200 may include, for example, one or more coils (e.g., dynamic magnetic stripe communications device 2204), a coil driver (e.g., ASIC 2202), processor 2206, excitation device (e.g., oscillator 2248) and one or more sensors (e.g., sensor 844 and/or sensor 2266).
  • coils e.g., dynamic magnetic stripe communications device 2204
  • a coil driver e.g., ASIC 2202
  • processor 2206 e.g., excitation device (e.g., oscillator 2248) and one or more sensors (e.g., sensor 844 and/or sensor 2266).
  • excitation device e.g., oscillator 2248
  • sensors e.g., sensor 844 and/or sensor 2266.
  • Dynamic magnetic stripe communications device 2204 may, for example, include a first coil (e.g., coil 2250) for communicating a first track of magnetic stripe information to a read head of a magnetic stripe reader, a second coil (not shown) for communicating a second track of magnetic stripe information to the read head of the magnetic stripe reader and a third coil (not shown) for communicating a third track of magnetic stripe information to the read head of the magnetic stripe reader.
  • a first coil e.g., coil 2250
  • second coil not shown
  • third coil not shown
  • Any one or more coils of dynamic magnetic stripe communications device 2204 may be used in a first mode of operation as a magnetic stripe communications device and in a second mode of operation, dynamic magnetic stripe communications device 2204 may be used as a component of inductive detection circuitry 2200.
  • processor 806 may activate ASIC 2202 (e.g., via assertion of signal ENABLE1 of ASIC 2202), which may in turn cause ASIC 2202 to assert a signal (e.g., ASIC 2202 may assert signal VPOS to an active high voltage level).
  • switch devices e.g., NFET 2208 and NFET 2210 may transition to a conductive state, thereby coupling ASIC 802 to one or more coils of dynamic magnetic stripe communications device 804 (e.g., node 2256 is electrically coupled to ASIC 2202 via NFET 2210 and node 2252 is electrically coupled to ASIC 2202 via NFET 2208).
  • processor 2206 may deactivate ASIC 2202 (e.g., via deassertion of signal ENABLE1 of ASIC 2202), which may in turn cause ASIC 2202 to deassert a signal (e.g., ASIC 2202 may deassert signal VPOS to an inactive low voltage level).
  • switch devices e.g., NFET 808 and NFET 2210 may transition to a non-conductive state, thereby decoupling ASIC 2202 from one or more coils of dynamic magnetic stripe communications device 2204 (e.g., node 2256 is electrically isolated from ASIC 2202 via NFET 2210 and node 2252 is electrically isolated from ASIC 2202 via NFET 2208).
  • processor 806 may assert signal, ENABLE2, thereby activating oscillator 2248, sensor circuit 2244 and/or sensor circuit 2246 during the second mode of operation.
  • Oscillator circuit 2248 may, for example, include an operational amplifier (OP AMP 2228), a feedback network (e.g., resistors 2230 and 2232) and a frequency selection network (e.g., resistors 2234, 2240 and capacitors 2236, 2238).
  • VREF1 may, for example, be a reference voltage (e.g., ground potential) when OP AMP 2228 operates between positive and negative power supply rails (e.g., an output signal generated by OP AMP 2228 is a signal having a direct current (DC) component at or near ground potential).
  • DC direct current
  • VREF1 may, for example, be a reference voltage (e.g., a positive potential greater than ground potential) when OP AMP 2228 operates between a positive power supply rail and ground potential (e.g., an output signal generated by OP AMP 2228 is a signal having a direct current (DC) component at a positive potential above ground potential).
  • a reference voltage e.g., a positive potential greater than ground potential
  • an output signal generated by OP AMP 2228 is a signal having a direct current (DC) component at a positive potential above ground potential
  • Oscillator circuit 2248 may, for example, generate a signal (e.g., a square wave signal) having a frequency that may be selected by a frequency selection network (e.g., resistors 2234,2240 and capacitors 2236,2238), where resistors 2234,2240 may be selected to have equivalent resistance magnitudes approximately between 1500 ohms and 5000 ohms (e.g., approximately 3300 ohms) and capacitors 2236,2238 may be selected to have equivalent capacitance magnitudes approximately between 20 and 80 pF (e.g., approximately 47 pF).
  • a frequency selection network e.g., resistors 2234,2240 and capacitors 2236,2238
  • Feedback network (e.g., resistors 2230 and 2232) of oscillator circuit 2248 may, for example, be used to select a voltage gain of OP AMP 2228, such that the overall gain of oscillator circuit 2248 is at, or near, unity when a signal at frequency, fosc, is being generated. Accordingly, for example, a ratio of the resistance magnitude of resistor 2230 to the resistance magnitude of resistor 2232 may be approximately between 2 and 10 (e.g., approximately equal to 5).
  • oscillator circuit 2248 may generate a signal to directly or indirectly excite a portion of dynamic magnetic stripe communications device 804 (e.g., center-tap node 2254 of coil 2250).
  • the signal may transition transistor 2242 between conductive and non-conductive states, thereby applying a signal (e.g., a voltage signal approximately equal to ground potential) to node 2254 when transistor 2242 is conductive and applying a signal (e.g., a voltage signal approximately equal to VREF2) to node 2254 when transistor 2242 is non- conductive.
  • a signal e.g., a voltage signal approximately equal to VREF2
  • a signal (e.g., a voltage signal) that may be indicative of an excitation of at least one coil of dynamic magnetic stripe communications device 2204 during the second mode of operation may be sensed by sensor 2244 and/or 2246 at nodes 2252 and/or 2256, respectively.
  • One or more differential amplifiers e.g., amplifier 2212 and/or 2220
  • amplifier 2212 and/or 2220 may, for example, be used to sense the difference between a signal present at a node (e.g., node 2252) as compared to a signal present at a different node (e.g., node 2256).
  • sensors 2244 and/or 2246 may provide a difference signal (e.g., a signal indicative of a zero difference) to indicate that no object may be in a touch, or proximity, relationship to dynamic magnetic stripe communications device 804 during the second mode of operation.
  • a difference signal e.g., a signal indicative of a zero difference
  • sensors 2244 and/or 2246 may provide a difference signal (e.g., a signal indicative of a non- zero difference) to indicate that an object may be in a touch, or proximity, relationship to dynamic magnetic stripe communications device 804 during the second mode of operation.
  • a difference signal e.g., a signal indicative of a non- zero difference
  • Differential amplifier 2212 of sensor 2244 may, for example, provide a difference signal that is indicative of a magnitude of a signal present at node 2252 subtracted from a magnitude of a signal present at node 2256.
  • Differential amplifier 2220 of sensor 2246 may, for example, provide a difference signal that is indicative of a magnitude of a signal present at node 2256 subtracted from a magnitude of a signal present at node 2252.
  • Peak detector 2214 may, for example, receive a difference signal generated by differential amplifier 2212 and/or peak detector 2222 may, for example, receive a difference signal generated by differential amplifier 2220. Excursions (e.g., maximum positive excursions) of the difference signal generated by differential amplifier 2212 and/or differential amplifier 2220 may, for example, forward bias a diode of peak detector 2214 and/or 2222, which may allow a capacitor of peak detector 2214 and/or 2222 to charge to a voltage indicative of such a maximum positive excursion, where the voltage may be maintained by the capacitor for a period of time (e.g., time enough for the difference signal generated by differential amplifier 2212 and/or differential amplifier 2220 to be sensed and processed by processor 2206).
  • a period of time e.g., time enough for the difference signal generated by differential amplifier 2212 and/or differential amplifier 2220 to be sensed and processed by processor 2206.
  • a resistance may, for example, be placed in parallel with the capacitor of peak detector 2214 and/or 2222 in order to allow the capacitor of peak detector 2214 and/or 2222 to discharge after a period of time (e.g., after the difference signal generated by differential amplifier 2212 and/or differential amplifier 2220 has been sensed and processed by processor 2206).
  • Comparators 2216 and 2224 of sensors 2244 and 2246, respectively may compare the maximum positive signal excursions as may be generated by peak detectors 2214 and 2222, respectively, to a reference potential (e.g., VREF3 and VREF4, respectively). Comparator 2216 may, for example, compare a maximum of the difference signal, V2256-V2252, as may be generated by peak detector 2214, to VREF3, where V2256 is the voltage at node 2256 and V852 is the voltage at node 2252.
  • an output of comparator 2216 (e.g., signal SENSEI) may be at a logic high level, whereas if the difference signal is above VREF3, then an output of comparator 2216 (e.g., signal SENSEI) may be at a logic low level.
  • Resistor 2218 may be used to provide hysteresis, so that an output of comparator 2216 does not oscillate when a magnitude of the difference signal present at the inverting input to comparator 2216 is at, or near, the magnitude of VREF3.
  • comparator 2224 may, for example, compare a maximum of the difference signal, V2252-V2256, as may be generated by peak detector 2222, to VREF4, where V2256 is the voltage at node 2256 and V2252 is the voltage at node 2252. If the difference signal is below VREF4, then an output of comparator 2224 (e.g., signal SENSE2) may be at a logic high level, whereas if the difference signal is above VREF4, then an output of comparator 2216 (e.g., signal SENSE2) may be at a logic low level. Resistor 2226 may be used to provide hysteresis, so that an output of comparator 2224 does not oscillate when a magnitude of the difference signal present at the inverting input to comparator 2224 is at, or near, the magnitude of VREF4.
  • Processor 2206 may, for example, monitor signals, SENSEI and/or SENSE2, as may be produced by sensors 2244 and/or 2246, respectively, to make a determination as to whether an object (e.g., a read head of a magnetic stripe reader) is in a proximity, or touch, relationship to dynamic magnetic stripe communications device 804 during the second mode of operation.
  • an object e.g., a read head of a magnetic stripe reader
  • FIG. 23 shows force detection circuitry 2300.
  • force detection circuitry 2300 may include, for example, comb electrodes 2320 and 2330 on a substrate 2340.
  • Comb electrodes may be conductive, for example, a metal (e.g., copper, silver and/or gold).
  • Substrate 2340 may be a support layer and/or an insulating layer.
  • substrate 2340 may be a layer of a flexible circuit board (e.g., polyimide and/or FR4).
  • Comb electrodes 2320 and 2330 may be, for example, circuit board traces connected to a processor. Contact resistance between electrodes 2320 and 2330 may vary as a response to the pressure applied to the pressure sensitive area.
  • the length L of force detection circuitry 2300 may be 8mm to 12mm, for example, 9mm to 11mm (e.g., about 10.5mm), and a width W of force detection circuitry 2300 may be 3mm to 6mm, for example, about 4mm to 5mm (e.g., about 4.5mm).
  • Example embodiments are not limited to a resistive electrode force sensors.
  • Force sensors may include, for example, piezoresistive, capacitive, electromagnetic piezoelectric, optical, resonant, thermal and/or ionization based sensors.
  • a force sensor may be a micro- electro-mechanical (MEMs) diaphragm sensor.
  • FIG. 24 shows card 2400.
  • card 2400 may be, for example, a card compliant or noncompliant with ISO specifications for identification cards.
  • card 2400 may be a flexible mobile telephonic device with a thickness compatible with magnetic stripe readers, for example, a mobile phone with the dimensions of a standard credit card, (i.e., a thickness of about 30mils, a length of about 3.370 inches and a width of about 2.125 inches).
  • card 1000 may be a telephonic apparatus with a length and width and width of a conventional mobile phone.
  • Card 2400 may include force sensor 2410 and EMV contacts 2420.
  • Force sensor 2410 may, be located in a region 2450 of card 2400 in which a feed wheel of a motorized reader (e.g., motorized reader of an automated teller machine (ATM)) contacts card 2400.
  • a feed wheel of a motorized reader e.g., motorized reader of an automated teller machine (ATM)
  • lines 2430 and 2440 may illustrate borders of region 2450.
  • a feed wheel of a motorized reader may contact and traverse card 2400 in region 2450.
  • the width X of region 1050 may be about, for example, 8mm.
  • Force sensor 1010 may be in proximity to or within region 2450 and embedded in card 2400 (e.g., a powered card). Although force sensor 2410 is shown in a particular location, such positioning is for illustrative purposes only. According to some example embodiments, force sensor 2410 may be anywhere in region 2450. According to other example embodiments, force sensor 2410 may be anywhere in card 1000 and still detect the presence of a feed wheel.
  • FIG. 25 a graph illustrating a force sensor response, for example, a signal associated with the detection of a motorized reader component (e.g., a feed wheel) crossing a high range force sensor of a powered card.
  • the response signal may be a signature from which the type of a reader, and a speed of the card relative to the reader, may be determined.
  • the velocity of the card relative to a reader may be determined using the dimensions of the sensor, for example, a dimension of a sensor across which a reader component crosses, and the width of the waveform produced by the force sensor (i.e., time).
  • the speed a card is moved by the feed wheel of a motorized reader may be used to determine a communication data rate (e.g., in bits per second (bps)).
  • the data rate may be determined so that, for example, data is transmitted to a read head of a motorized reader by a dynamic magnetic communications device of the card at the rate expected by the motorized reader.
  • the motorized reader may expect data to be communicated at a rate corresponding to the speed a magnetic stripe card would be moved across one or more read-heads of the motorized reader.
  • a magnetic stripe card may have multiple tracks of data written to the stripe at different data densities. For example, for a payment card, tracks one and three may be recorded at 210 bits per inch and track two may be recorded at 75 bits per inch. The velocity at which the reader moves the card across a read-head may be multiplied with the recording density to determine the data rate in bits per second. The card may communicate data with a dynamic magnetic communications device at a data rate matching the expected data rate.
  • a type of the reader may be determined based on, for example, a depth of the waveform produced by the force sensor as the reader exerts pressure on the card.
  • the depth of the waveform may be proportional to the force exerted on a card by the feed wheel of a motorized reader.
  • Each type of reader i.e., make and model
  • Signals produced or processed by a force sensor that do not match a known signature may be disregarded as a false detection. For example, pressure of a user's finger or of a wallet may be ignored.
  • the expectations of a type of reader may be characterized using a card configured to collect data and default rates of data communication may be used for user cards based on the type of the reader without knowledge of a velocity of the card in the motorized reader.
  • FIG. 26 shows a detection method flow diagram.
  • a sensor state change e.g., an increased capacitance
  • a second type of sensor may be activated in response to the sensor state change (e.g., as in step 2611).
  • a state of the second type of sensor e.g., an inductive detection of a conductive object
  • may be determined e.g., as in step 2612).
  • a state change of a third type of sensor may be used to detect a type of a reader (e.g., a motorized reader or a make/model of a reader) (e.g., as in step 2613).
  • a communication sequence may be activated (e.g., as in step 2614) and/or the second type of sensor may be deactivated.
  • Example embodiments are not limited and, for example, although the state change of the third type of sensor is shown after step 2612, the state change is independent and may occur at any time in the sequence.
  • FIG. 27 shows an example card according to example embodiments.
  • card 2705 illustrates an exemplary card prior to pushing a button on the card.
  • Card 2755 illustrates the same exemplary card after pushing a button on the card once the display has completed updating.
  • initially information regarding one stored card in this case the Visa 1 card, is displayed. While not shown, additional information can be displayed to the user on the same or different displays.
  • the card number may be displayed in an embodiment.
  • the Visa® logo may be displayed.
  • the EMV chip Prior to pressing the button, the EMV chip will communicate information associated with the Visa 1 card that is displayed on card 2705.
  • the Visa 1 card information may also be communicated via multiple means, for example a dynamic magnetic stripe emulator, a dynamic magnetic stripe encoder, or wirelessly.
  • the Visa 1 card information may also be communicated wirelessly via Bluetooth, RFID, WiFi, light (using LEDs and light sensors), as well as other wireless communication means known to those skilled in the art.
  • the display After pressing the button, the display will update, as described in more detail below, to display the information associated with a second cards, for example the VISA 2 card.
  • the display will appear to be swiped clear from a left to right direction. Once the display has been cleared, information regarding the second card will appear on the display, again in a left to right direction. Further exemplary embodiments are described below.
  • the EMV chip will communicate information associated with the Visa 2 card that is displayed on card 2755.
  • the Visa 2 card information may also be communicated via multiple means, for example a dynamic magnetic stripe emulator, a dynamic magnetic stripe encoder, or wirelessly.
  • the Visa 2 card information may also be communicated wirelessly via Bluetooth, RFID, WiFi, light (using LEDs and light sensors), as well as other wireless communication means known to those skilled in the art.
  • card 2705 maybe able to be recharged wirelessly, for example via a user's mobile phone.
  • FIG. 28 shows an example card according to example embodiments.
  • display 2810 illustrates an exemplary display card.
  • the display may be blank, for example when the card is in a sleep mode.
  • a processor for example a 16 bit microprocessor, an ARM processor, or processor 120 illustrated in figure 1, may be configured to provide information to be displayed on display 2810 to a driving circuit that will in turn drive display 2810.
  • the driving circuit is configured to drive display 2810 to display the image from left to right.
  • the image may gradually appear, row by row, on display 2810.
  • the processor may control the driver to drive the display to first display the right most column of pixels in the left most column, and then display the right 2 most column of pixels in the left 2 most columns, and continue until the entire image is displayed, making is appear like the image moved across the screen.
  • the image may appear from top to bottom, bottom to top, or right to left.
  • the display may be display a first card's information.
  • the card may be configured to provide information regarding a second card to be displayed on display 2810 to a driving circuit that will in turn drive display 2810.
  • the driving circuit is configured to drive display 2810 to display the image from left to right.
  • an image associated with the first card may gradually disappear, row by row, on display 2810 and then an image associated with the second card may gradually appear. This may happen in various ways known to those skilled in the art, for example those described above.
  • an image associated with the first card may gradually disappear, row by row, on display 2810, while at the same time an image associated with the second card may gradually appear. This may happen in various ways known to those skilled in the art, for example those described above.
  • the image data provided by the processor may be compressed image data.
  • the image data stored on the card may be compressed image data.
  • the image data may be compressed by the processor, prior to sending the image data to the driving circuit.
  • image data associated with the payment cards stored on the card are loaded onto the card at the time the card is issued.
  • image data associated with user cards may be added or removed from the card as user cards are added or removed from the card.
  • an issuer or financial institution may communicate new card information wirelessly, such as using Bluetooth, WiFi, or NFC communications, or using wired connections, such as the EMV contacts, to the card.
  • the new card information may include image data.
  • this image data is stored directly to the memory on the card.
  • the processor processes this image data and stores a compressed version of the card image to memory.
  • Image data associated with a user card stored on the card may include new credit card numbers, new expiration dates, new network logos, coupon images, reward card images, point card images, hotel card images, barcodes, qcodes, CVV/CVC, dynamic CVV/CVC algorithms, dynamic CVV/CVC keys, etc.
  • FIG. 29 shows an example card according to example embodiments.
  • the display comprises a first portion 2910 and a second portion 2920.
  • the first portion 2910 may be updated first as described above, followed by the second portion 2920.
  • second portion 2920 may be updated first, followed by first portion 2910.
  • first portion 2910 may be updated at the same time as second portion 2920, for example to create the effect that the display is being updated from the middle up and down, for from the left to the right on the time and from the right to the left on the bottom, or from the top and bottom towards the middle.
  • a person skilled in the art would understand that these are merely examples and that other configurations are possible.
  • FIG. 30 shows an example card according to example embodiments.
  • the display comprises a first portion 3005, second portion 3010, third portion 3015, and fourth portion 3020.
  • each of the portions may be updated sequentially, for example first the first portion, followed by the second portion, then the third portion, and finally the fourth portion (though the portions may be updated in any order).
  • two or more of the portions may be updated at the same time, for example all four portions may be updated simultaneously. This may allow for the display to provide different affects, such as updating the display from the center out or from the corners in. A person skilled in the art would understand that these are merely examples and that other configurations are possible.
  • FIG. 31 includes electronics package 3100 that may be included, for example, on a circuit board of an interactive payment card such as an interactive debit and/or credit card.
  • Electronics package 3100 may include any number of pressure sensors such as, for example, pressure sensors 3110 and 3120.
  • a payment card terminal may be motorized and may automatically receive payment cards. Wheels may be utilized on such a motorized payment card reader to move a card throughout a reader. Such wheels may be detected by one or more pressure sensors.
  • Pressure sensors may be located at any location of a card such as, for example, the top of the card, middle of the card, and/or bottom of the card.
  • one or more pressure sensors about the top of a card may detect one or more wheels about the top of a card.
  • One or more pressure sensors about the middle of a card may detect one or more wheels about the middle of a card.
  • One or more pressure sensors about the bottom of a card may detect one or more wheels about the bottom of a card.
  • Any number of pressure sensors may be utilized to detect a wheel.
  • one, two, three, or more than three pressure sensors may be utilized to detect a wheel.
  • Multiple pressure sensors may be spaced apart so that a wheel moves across the multiple pressure sensors and the movement is detected. Accordingly for example, the time difference between the detection of a wheel by multiple (e.g., two) pressure sensors may be utilized to determine the velocity of a card through a reader.
  • Such a velocity may be utilized, for example, by a card so the card can provide data (e.g., magnetic stripe data such as one, two, or three tracks of magnetic stripe data) at a rate associated with the determined speed.
  • Pressure sensors may be used in conjunction with other sensors (e.g., capacitive sensors, indicative sensors, hall effect sensors) to assist in determine different types of readers and an interactive payment card may have different firmware for operating in different types of readers (e.g., a first type of motorized reader or a second type of motorized reader).
  • Card may keep stored sensor values from one or more types of sensors and utilize data from these stored values to determine a type of reader and communicate data in a form associated with that reader. For example, magnetic data may be communicated at different speeds, with different leading/trailing zeros, for different tracks, with different delays, etc., for different types of detected readers.
  • Pressure sensor 3110 may include conductive traces 3111 and 3112.
  • Pressure sensor 3120 may include conductive traces 3121 and 3122.
  • electronics package 3110 may be placed on a card rotated 90 degrees as shown in FIG. 31 so that a wheel moving from left-to-right or right-to- left on the surface of the card will move over both sensors 3110 and 3120.
  • Sensors 3110 and 3120 may, for example, determine the direction a motorized reader is swiping.
  • motorized readers may move a card through one or more read-heads (e.g., a JIS1 read-head on one side of a card and a JIS-2 read-head on another side of a card) multiple times, for example, if a card is not read on the first try.
  • a processor may utilize information from pressure sensors to change the way data is communicated each time the card is attempted to be read by a motorized reader.
  • Flow chart 3150 may be included and may include step 3151 in which a timer is started after a first pressure sensor signal from a first pressure sensor is received. The timer may be stopped, for example, after a second pressure signal from a second pressure sensor is received in step 3152. The time between the two actuations of the pressure sensors may be determined in step 3163 and the distance the wheel traveled may be determined in step 3154 and the velocity the wheel was travelling may be determined in step 3156 and data, such as magnetic stripe data, may be communicated based on such a determined velocity.
  • the distance may be a known distance between pressure sensor 3110 and 3120 (e.g., a known distance from the long axis of pressure sensor 3110 to the long axis of pressure sensor 3120).
  • a transmission rate from a dynamic magnetic stripe communications device may be determined based on a velocity so the transmission rate is approximate to the rate at which a read head may read data for a card traveling at the determined velocity.
  • Multiple velocity bins may be determined and each bin may be associated with different velocity ranges. Once a velocity is determined, a bin may be selected based on the range of the bin and the velocity determined so the bin velocity range matches the determined velocity. A transmission rate associated with the bin may then be utilized.
  • a card may have more than one magnetic stripe data tracks for communication on more than one magnetic communications device.
  • a magnetic communications device may communicate information to a magnetic stripe read- head located on the obverse side of a card (e.g., an EMV contact chip side) such as and one or more magnetic communications devices may communication information to a magnetic stripe read-head located on the reverse side of a card.
  • multiple communications devices may communicate simultaneously to both JIS-1 and JIS-2 read-heads. Different communication processes (e.g., communication rates) may be associated with a particular velocity (e.g., bin velocity range) for different read-heads.
  • one or more pressure sensors may be utilized with multiple other types of sensing technologies on a card, or other device.
  • capacitive sensing may be utilized to determine that a read-head of a magnetic stripe reader electronically couples with the capacitive sensing. After capacitive sensing determines a read- head, one or more inductive sensors may be turned ON to confirm a read-head is interfacing with the inductive sensor.
  • inductive sensors may be utilized to determine, for example, the direction a card is being swiped or read by a reader. Inductive sensors may also provide an magnitude and a certain threshold may determine if a read-head is at a certain point with respect to one or more inductive sensors.
  • One or more pressure sensors may be positioned to provide a signal before this inductive sensing threshold is met. Accordingly, velocity of the read-head may be determined and associated magnetic communications device communication attributes may be determined and then utilized when, for example, the inductive threshold is met.
  • one or more pressure sensors may be located close to a card edge (e.g., the left card edge from the obverse side of a card). For example, one or more pressure sensors may be located within an inch, within half an inch, or within a quarter of an inch of a edge of a card.
  • capacitive sensing may be OFF while a card is OFF.
  • Turning a card ON e.g., selecting a payment option and/or account
  • Hall sensors may be utilized to determine a read- head configuration (e.g., whether a read-head is located on one side of a card, both sides of a card, and whether the read heads are aligned with respect to one another or offset and, if offset, which read-head is the first to pass over a card and which read-head is the second to pass over a card).
  • Hall sensors may, for example, activate inducting sensing.
  • Pressure sensor(s) may be positioned to detect one or more wheels before a triggering threshold of an inductive sensing is met. After pressure sensors determine one or more wheels (e.g., as well as a velocity), Hall Sensor data may be utilized to determine a type of reader. For example, certain readers may be fabricated with a particular amount of metal, a reader with a large amount of metal may cause a certain communications attribute (e.g., a particular velocity may be determined and a particular communication data rate may be determined). If the hall effect sensors, for example, do not determine a particular type or types of readers that are associated with particular type or types of communication attributes, a determined velocity may be utilized for communication data rate.
  • Hall Sensor data may be utilized to determine a type of reader. For example, certain readers may be fabricated with a particular amount of metal, a reader with a large amount of metal may cause a certain communications attribute (e.g., a particular velocity may be determined and a particular communication data rate may be determined). If the hall effect sensors, for example, do not determine
  • Readers e.g., readers with a large amount of metal
  • readers may utilize a single track of data (e.g., Track 2 data) and other types of readers, for example, may utilize multiple or several tracks of data.
  • Persons skilled in the art will appreciate that any number of pressure sensors (e.g., three or more) may be utilized for a single wheel to determine velocity and change in velocity (e.g., acceleration).
  • one or more pressure sensors may be utilized at the top edge of a card (with respect to an obverse side of a card that includes contact reader contacts).
  • a card may be turned ON, capacitive sensing may turn ON, inductive sensing may be turned ON after capacitive sensing detects a read- head, the pressure sensor may determine a wheel before a threshold of inductive sensing is reached.
  • Card velocity may be determined or, for example, card velocity may be associated with a determined reader associated with a top-edge sensor (e.g., all instances a top-edge pressure sensor detects one or more wheels).
  • FIG. 32 shows a view of a pressure sensing system 3201 and cross-section 3230 taken along line A-A' of pressure sensing system 3201.
  • pressure sensing system 3201 may include base layer 3235, separation layer 3215 and pressure sensitive conductive layer 3240 (not shown in pressure sensing system 3201 for clarity of explanation).
  • Separation layer 3215 may include spaces 3205 and 3210.
  • Base layer 3235 may include a material (e.g., flex material or thin FR-4), with active area sensors (not shown) on and/or in the material and exposed by spaces 3205.
  • Contacts 3220 may correspond to the active area sensors. For example, one contact may connect to an active area sensor in space 3205, another contact may connect to an active area sensor in space 3210, and a third contact may be a ground (e.g., a contact between the active area sensor contacts).
  • Separation layer 3215 may include an adhesive, for example, a double sided pressure sensitive adhesive tape (e.g., bond ply). Separation layer 3215 may be separate pressure sensitive conductive layer 3240 from the active area sensors of base layer 3235 (or on base layer 3235). Pressure sensitive conductive layer 3240 may be a force sensing resistive layer with a resistance varying as a function of applied force. For example, the resistance of pressure sensitive conductive layer 3240 may decrease as force is applied.
  • an adhesive for example, a double sided pressure sensitive adhesive tape (e.g., bond ply).
  • Separation layer 3215 may be separate pressure sensitive conductive layer 3240 from the active area sensors of base layer 3235 (or on base layer 3235).
  • Pressure sensitive conductive layer 3240 may be a force sensing resistive layer with a resistance varying as a function of applied force. For example, the resistance of pressure sensitive conductive layer 3240 may decrease as force is applied.
  • pressure sensing system 3201 may be used in, for example, a powered card.
  • a powered card may be inserted into a motorized reader.
  • a wheel (e.g., feed wheel) of the motorized reader may cross the active are sensors, for example, cross over one active area sensor and then a second active area sensor.
  • Separation layer 3215 may separate pressure sensitive conductive layer 3240 from the active area sensors when no wheel applies pressure, and pressure sensitive conductive layer 3240 may contact the active area sensors through spaces 3205 and 3210 when pressure is applied, for example, by a feed wheel.
  • the resistance of pressure sensitive conductive layer 3240 may decrease and short circuit conductive lines of the active area sensors when the wheel crosses over spaces 3205 and 3210.
  • a distance between the centerlines of the two active area sensors of pressure sensing system 3201 and/or the separation between the active area sensors by layer 3215 may be selected so that the active area sensors are close enough together for velocity to be calculated prior to the card being too far into the motorized reader, for timely and/or accurate communication with the reader (e.g., to avoid card read failures).
  • pressure sensing system 3201 may be connected to a processor of a powered card. Pressure from the wheel of a motorized reader may force pressure sensitive conductive layer 3240 against the active area sensors exposed by spaces 3205 and 3210 and reduce the resistance of pressure sensitive conductive layer 3240 the tracks in the active area sensors together so that the card processor receives a signal indicative of a change in state across terminals (e.g., two terminals).
  • Distance 3250 may be 0.5 inches to 1.0 inches, for example, about 0.8 inches (e.g., 0.818 inches).
  • Distance 3255 may be 0.01 inches to 0.03 inches, for example, about 0.02 inches (e.g., 0.021 inches).
  • Distance 3260 may be 0.04 inches to 0.06 inches, for example, about 0.050 inches (e.g., 0.049 inches).
  • Distance 3265 may be 0.01 inches to 0.03 inches, for example, about 0.02 inches (e.g., 0.021 inches).
  • Distance 3270 may be 0.01 inches to 0.02 inches, for example, about 0.15 inches (e.g., 0.151 inches).
  • Distance 3275 may be 0.020 inches to 0.040 inches, for example, about 0.030 inches.
  • FIG. 33 shows card 100 that may include, for example, dynamic magnetic stripe communications device 101, one or more displays (e.g., displays 112, 113 and 125), permanent information 120, light sensor 127, one or more buttons (e.g., buttons 130-134, 198 and 199), lights 135-138, 196 and 197, and dynamic number 114 which may include a permanent portion 111.
  • Permanent portion 111 may be, for example, printed, embossed and/or laser etched on card 100.
  • Display 112 may display a dynamic number entirely, and/or partially.
  • Display 113 may be utilized to display a dynamic code (e.g., a dynamic security code).
  • Display 125 may display logos, barcodes, and/or one or more lines of information (e.g., may display a coupon code).
  • a display e.g., at least one of displays 112, 113 and 125
  • a bi-stable display may be a display that maintains an image without power.
  • Card 100 may include permanent information 120 including, for example, information specific to a user (e.g., a user's name and/or username) and/or information specific to a card (e.g., a card issue date and/or a card expiration date).
  • information specific to a user e.g., a user's name and/or username
  • information specific to a card e.g., a card issue date and/or a card expiration date.
  • Card 100 may include a dynamic magnetic communications device.
  • a dynamic magnetic communications device may take the form of a magnetic encoder and/or a magnetic emulator.
  • a magnetic encoder may change the information located on a magnetic medium such that a magnetic stripe reader may read changed magnetic information from the magnetic medium.
  • a magnetic emulator may generate electromagnetic fields that directly communicate data to a magnetic stripe reader. Such a magnetic emulator may communicate data serially to a read-head of the magnetic stripe reader.
  • Card 100 may include one or more buttons, for example, buttons 130-134, 198 and 199.
  • Buttons 130-134, 198 and 199 may be, for example, mechanical buttons, capacitive buttons, light sensors and/or a combination thereof.
  • Button 199 may be used, for example, to communicate information through dynamic magnetic stripe communications device 101 indicative of a user's desire to communicate a single track of magnetic stripe information.
  • a button e.g., button 199
  • pressing a button may cause information to be communicated through device 101 when an associated read-head detector detects the presence of a read-head of a magnetic stripe reader and/or at a specific frequency.
  • Button 198 may be utilized to communicate (e.g., after button 198 is pressed and after a read-head detects a read-head of a reader) information indicative of a user selection (e.g., to communicate two tracks of magnetic stripe data).
  • Multiple buttons may be provided on a card and each button may be associated with a different user selection.
  • buttons 198 and button 199 may each be associated with, for example, a different third party service provider feature (e.g., an application facilitating a coupon) and may be changed by a user at any time.
  • a different third party service provider feature e.g., an application facilitating a coupon
  • a user may select a third party feature from a list displayed to the user. For example, the user may scroll through a list of features on a display (e.g., display 125). A user may scroll through a list using buttons on a card (e.g., buttons 130-134). The list of features may be displayed to the user individually, in groups and/or all features may be simultaneously displayed.
  • a display e.g., display 125
  • buttons on a card e.g., buttons 130-134
  • a third party feature associated with a button may be changed by a user, for example, on a graphical user interface (GUI) provided by a device provider, ecosystem provider, application manager provider, remote facility provider, card issuer, processor, and/or any other entity (which may be the same or different entities).
  • GUI graphical user interface
  • an ecosystem provider may, on its website and/or via an application, allow a user to change the third party feature performed when the third party's feature button is selected by a user on the user's card or other device.
  • a third party service provider may provide a reward (e.g., a coupon) from a collection of rewards based on, for example, one or more card transactions.
  • the fact the user has received the reward may be presented on a profile page of the user.
  • a user's profile may be updated to state that the user has earned a reward and the user may receive the reward (e.g., via email).
  • a user may be provided with a GUI, for example, a GUI on a mobile telephonic device of the user, when the user makes a purchase, to identify and/or use the reward earned by the user.
  • the selection of a feature may or may not have a cost associated with it. If a cost is associated with the feature, for example, the cost may be added to a customer's statement (e.g., added to a credit or debit purchase) for a particular transaction. A fixed-fee or variable-fee (e.g., a percentage of the transaction) may then be removed from the fee charged to the user and distributed among particular parties (e.g., distributed to the card issuer, application manager provider, ecosystem provider, device provider and/or other entity). The remainder of the fee, if any, may be provided, for example, to the third party service provider.
  • a cost may be added to a customer's statement (e.g., added to a credit or debit purchase) for a particular transaction.
  • a fixed-fee or variable-fee e.g., a percentage of the transaction
  • parties e.g., distributed to the card issuer, application manager provider, ecosystem provider, device provider and/or other entity.
  • a cost may be associated to a feature selection, but may not be a cost to a user.
  • the cost may be a cost to a third party service provider (e.g., an incentive).
  • the cost may be a cost to other entities, for example, the device provider, card issuer, card processor (which may be the same, for example, as the card issuer), and/or any other entity (e.g., card network).
  • a user may select a type of payment on card 100 via manual input interfaces (e.g., buttons 130-134).
  • the manual input interfaces may correspond to displayed options (e.g., displayed on display 125).
  • Selected information may be communicated to a magnetic stripe reader via a dynamic magnetic stripe communications device.
  • Selected information may also be communicated to a device (e.g., a mobile telephonic device) including a capacitive sensor and/or other type of touch sensitive sensor.
  • Lights 135-138, 196 and 197 may be associated with buttons 131-134, 198 and 199.
  • Each of lights 135-138, 196 and 197 may indicate, for example, when a button is pressed.
  • a light may begin blinking to indicate card 100 is still active (e.g., for a period of time) while reducing power expenditure.
  • a light may be provided for button 130.
  • Card 100 may include light sensor 127.
  • Light sensor 127 may, for example, receive information from a light source (e.g., a display of a mobile telephonic device and/or a laptop computer).
  • Card 100 may include, for example, any number of light sensors 127.
  • Light sensor 127 may be utilized such that a display screen, or other light emitting device, may communicate information to light sensors 127 via light.
  • Display 125 may allow a user to select (e.g., via buttons) options on display 125 that instruct the card to communicate (e.g., via a dynamic magnetic stripe communications device, RFID and/or exposed IC chip) to use a debit account, credit account, pre-paid account, and/or point account for a payment transaction.
  • Architecture 150 may be utilized with any card (e.g., any card 100).
  • Architecture 150 may include, for example, processor 120, display 140, driving circuitry 141, memory 142, battery 143, radio frequency identification (RFID) 151, integrated circuit (IC) chip 152, electromagnetic field generators 170, 180, and 185, and read-head detectors 171 and 172.
  • RFID radio frequency identification
  • IC integrated circuit
  • Processor 120 may be any type of processing device, for example, a central processing unit (CPU) and/or a digital signal processor (DSP). Processor 120 may be, for example, an application specific integrated circuit (ASIC). Processor 120 may include on-board memory for storing information (e.g., triggering code). Any number of components may communicate to processor 120 and/or receive communications from processor 120. For example, one or more displays (e.g., display 140) may be coupled to processor 120. Persons skilled in the art will appreciate that components may be placed between particular components and processor 120. For example, a display driver circuit may be coupled between display 140 and processor 120. [0578] Memory 142 may be coupled to processor 120.
  • CPU central processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • Processor 120 may include on-board memory for storing information (e.g., triggering code). Any number of components may communicate to processor 120 and/or receive communications from processor 120.
  • one or more displays e.g., display 140
  • a display driver circuit
  • Memory 142 may store data, for example, data that is unique to a particular card. Memory 142 may store any type of data. For example, memory 142 may store discretionary data codes associated with buttons of a card (e.g., card 100 of FIG. 33). Discretionary data codes may be recognized by remote servers to effect particular actions. For example, a discretionary data code may be stored in memory 142 and may be used to cause a third party service feature to be performed by a remote server (e.g., a remote server coupled to a third party service such as a coupon provider). Memory 142 may store firmware that, for example, controls triggering and/or the like.
  • Architecture 150 may include any number of reader communication devices.
  • architecture 150 may include at least one of IC chip 152, RFID 151 and a magnetic stripe communications device.
  • IC chip 152 may be used to communicate information to an IC chip reader (not illustrated).
  • IC chip 152 may be, for example, an EMV chip.
  • RFID 151 may be used to communicate information to an RFID reader.
  • RFID 151 may be, for example, an RFID tag.
  • a magnetic stripe communications device may be included to communicate information to a magnetic stripe reader.
  • a magnetic stripe communications device may provide electromagnetic signals to a magnetic stripe reader.
  • Electromagnetic field generators 170, 180, and 185 may include a coil (e.g., each may include a coil) wrapped around one or more materials (e.g., a soft-magnetic material and a non- magnetic material).
  • Each electromagnetic field generator may communicate information, for example, serially to a receiver of a magnetic stripe reader for a particular magnetic stripe track.
  • a single coil may communicate multiple tracks of data.
  • Architecture 150 may include read head detectors 171 and 172.
  • Read-head detectors 171 and 172 may be configured to sense the presence of a magnetic stripe reader (e.g., a read-head housing of a magnetic stripe reader). Information sensed by the read-head detectors 171 and 172 may be communicated to processor 120 to cause processor 120 to communicate information serially from electromagnetic generators 170, 180, and 185 to magnetic stripe track receivers in a read-head housing of a magnetic stripe reader.
  • a magnetic stripe communications device may change the information communicated to a magnetic stripe reader at any time.
  • Processor 120 may, for example, communicate user-specific and card-specific information through RFID 151, IC chip 152, and/or electromagnetic generators 170, 180, and 185 to card readers coupled to remote information processing servers (e.g., purchase authorization servers).
  • Driving circuitry 141 may be utilized by processor 120, for example, to control electromagnetic generators 170, 180 and 185.
  • Architecture 150 may include, for example, a light sensor. Architecture 150 may receive information from a light sensor. Processor 120 may determine information received by a light sensor.
  • FIG. 34 shows device 200 that may be, for example, a mobile telephonic device and/or other device (e.g., portable computer such as a portable tablet computer).
  • Device 200 may include, for example, housing 202, display 210, device card 220, virtual buttons 230, 231 and 240, virtual lights 242-247, dynamic card number and verification code 245, and identification information 250.
  • Display 210 may include, for example, light- sensitive and/or touch-sensitive elements.
  • Device 200 may communicate information to a card reader, for example, via a contactless signal (e.g., an RFID signal) and/or a contact-based signal (e.g., a USB connection).
  • a contactless signal e.g., an RFID signal
  • a contact-based signal e.g., a USB connection
  • Device 200 may include a device card 220 and/or virtual buttons 230 and 231.
  • Device card 220 may be a virtual representation of a card and/or any information identifying a payment method (e.g., credit account number).
  • a payment method e.g., credit account number
  • any physical card described herein may be provided as a device card on, for example, a computing system (e.g., a mobile telephonic device and/or a computer).
  • Physical buttons of a physical card may, for example, correspond to virtual buttons of a device card.
  • Virtual button 230 may, for example, correspond to one feature (e.g., an opportunity to earn a coupon) from a third party service provider while virtual button 231 may, for example, correspond to another feature (e.g., the opportunity to add value to a coupon) from the same or a different third party service provider.
  • every feature may not be provided by a third party service provider.
  • the device provider may provide features.
  • All features for a card may be utilized with a particular payment account (e.g., a credit account) such that a payment transaction with that payment account is performed if any feature is selected.
  • a payment account e.g., a credit account
  • an additional one or more features may be associated with a different payment account (e.g., a debit account).
  • a selected feature associated with a credit account may be utilized to make a purchase with credit and may perform an additional action associated with that feature.
  • a different selected feature associated with a debit account may be utilized to make a purchase with debit and may perform an additional action associated with that different feature.
  • Device 200 may include virtual lights 242-247.
  • Virtual lights 242-247 may, for example, indicate an active period during which device 200 may communicate with external devices.
  • Virtual lights 242-247 may correspond to, for example, virtual buttons 230, 231 and 240. According to example embodiments, a fewer or greater number of virtual lights are contemplated (e.g., a center button of virtual buttons 240 may virtually light up).
  • FIG. 35 shows network topology 300 that may include, for example, mobile device 302, contactless device 304, cellular network access infrastructure 306, mobile network 310, wireless access point 308, IP network 312, payment network 314, issuer 320, payment server 316, merchant acquirer 317, ecosystem provider 342, merchant terminal 318, transaction card 333, user electronic device 345 and/or application providers 338, 339 and 340.
  • Mobile device 302 may include, for example, a contactless interface that may initiate, sustain, and/or terminate communication channel 326 between contactless device 304 (e.g., a powered card, non-powered card and/or a device) and mobile device 302.
  • contactless device 304 e.g., a powered card, non-powered card and/or a device
  • Contactless device 304 and mobile device 302 may communicate via channel 326 using any number of contactless mediums, which may include for example, visible, audible, capacitive, electromagnetic, magnetic, and/or RF mediums.
  • Mobile device 302 may provide one or more transceivers, receivers and/or transmitters that may communicate with one or more wired networks (e.g., IP network 312 and/or payment network 314) and/or one or more wireless networks (e.g., a mobile network 310).
  • Mobile device 302 may, for example, communicate with a cellular station over a wireless radio interface (e.g., a GSM air interface) that may be used by mobile device 302 to communicate information (e.g., voice and data) to cellular network access infrastructure 306 (e.g., one or more GSM base transceiver stations, base station controllers and mobile switching centers).
  • cellular network access infrastructure 306 may utilize any multiple access architecture, such as for example, a code-division multiple access architecture and/or a time-division multiple access architecture.
  • Mobile device 302 may, for example, communicate with wireless access point 308 over a wireless interface (e.g., a Bluetooth interface or a Wi-Fi interface). Accordingly, for example, mobile device 302 may access one or more wired networks (e.g., IP network 312 and/or payment network 314) and/or one or more wireless networks 310 (e.g., a mobile network) without the need to first gain access to cellular network access infrastructure 306.
  • a wireless interface e.g., a Bluetooth interface or a Wi-Fi interface
  • wireless networks 310 e.g., a mobile network
  • Payment information may be communicated from contactless device 304 to mobile device 302 in support of a transaction (e.g., a financial transaction) being conducted by mobile device 302.
  • a transaction e.g., a financial transaction
  • IP network 312 e.g., the internet
  • Mobile device 302 may, for example, complete a purchase transaction by first obtaining required payment information from contactless device 304 and then communicating such payment information to network entities (e.g., merchant acquirer 317, payment server 316 and/or issuer 320).
  • network entities e.g., merchant acquirer 317, payment server 316 and/or issuer 320.
  • Mobile device 302 may, for example, already contain payment information necessary to complete a purchase transaction. Accordingly, mobile device may not need to obtain payment information from contactless device 304 before completing a purchase transaction.
  • Payment server 316 may, for example, contact issuer 320 via a network (e.g., payment network 314) with payment information received from mobile device 302 for authorization of a purchase. Once authorized, payment transaction information may be recorded onto a receipt that may be delivered to mobile device 302 via any one or more delivery options (e.g., via a short messaging service of mobile network 310 or an email delivery service of IP network 312).
  • a network e.g., payment network 314
  • payment transaction information may be recorded onto a receipt that may be delivered to mobile device 302 via any one or more delivery options (e.g., via a short messaging service of mobile network 310 or an email delivery service of IP network 312).
  • a payment receipt may, for example, be provided to mobile device 302 as a proof-of-purchase object (e.g., a barcode) that may be provided to a display of mobile device 302 and read by other computing equipment (e.g., a barcode scanner) for proof-of-purchase confirmation.
  • a proof-of-purchase object e.g., a barcode
  • other computing equipment e.g., a barcode scanner
  • Transaction card 333 may, for example, communicate information to merchant terminal 318 (e.g., a magnetic stripe reader, an EMV reader, an RFID reader, an NFC reader and/or a swipe reader attached to an electronic device).
  • Merchant terminal 318 may begin transactions (e.g., point-of-sale transactions) and/or complete transactions via merchant acquirer 317 and/or payment network 314. Accordingly, for example, transaction card 333 may communicate payment information to merchant terminal 318 to initiate a financial transaction.
  • Merchant terminal 318 may communicate transaction information, including at least a portion of the payment information, to merchant acquirer 317.
  • Merchant acquirer 317 may authorize the financial transaction and/or communicate with payment server 316.
  • Payment server 316 may, for example, contact issuer 320 via a network (e.g., payment network 314) with transaction information received from merchant acquirer
  • Application providers 338, 339 and 340 may be one or more entities (e.g., one or more servers) providing applications for association in an ecosystem provided by ecosystem provider 342.
  • Each application may provide one or more features to users of a payment method (e.g., users of contactless device 304 and/or transaction card 333).
  • a payment method e.g., users of contactless device 304 and/or transaction card 333.
  • an application may provide a user an opportunity to earn a coupon and/or add value to a coupon in exchange for using the payment method.
  • application provider 338 may provide coupons as part of a loyalty or rewards program, which may be independent of any payment method.
  • Ecosystem provider 342 may be, for example, a server that maintains associations between applications, users and payment methods.
  • Ecosystem provider 342, and application providers 338, 339 and 340 may communicate with different entities using one or more wired networks (e.g., IP network 312 and/or payment network 314) and/or one or more wireless networks 310 (e.g., a mobile network).
  • Application providers 338, 339 and 340 may communicate directly and/or indirectly with different entities.
  • merchant terminal 318 and/or ecosystem provider 342 may communicate directly with application providers 338, 339 and 340 via IP network 312 and/or via a direct connection (e.g., to validate coupons with a coupon server).
  • application providers 338, 339 and 340 may exchange information (e.g., transactional data) indirectly with issuer 320, merchant acquirer 317 and/or payment network 314 via, for example, ecosystem provider 342.
  • a user electronic device may display a GUI.
  • the GUI may be an application manager used to interface with ecosystem provider 342, and application providers 338, 339 and 340, to define user preferences.
  • Defining user preferences may include, for example, configuring associations (e.g., between users, applications and payment methods), features and/or permissions.
  • the GUI displayed on the user electronic device may, for example, display indicia representing applications that provide features.
  • a user may associate one or more of the applications to one or more payment cards and/or payment card buttons (e.g., mobile device 302 and/or transaction card 333)).
  • the GUI displayed on the user electronic device may be used to, for example, interface with one or more of application providers 338, 339 and 340.
  • application providers 338, 339 and 340 For example, using the GUI, a user may select a coupon from among multiple coupons provided by an application hosted by an application provider.
  • a user may use the GUI displayed on the user electronic device to define how payment network 314, ecosystem provider 342, one or more of application providers 338, 339 and 340, and third-party applications hosted by the one or more application providers (or any other application providing entity) interact for transactions conducted by the user.
  • a user may accept an end license user agreement that outlines how data may be shared between entities.
  • a user may define what data may be shared between entities.
  • data e.g., transactional data
  • ecosystem provider 342 may be provided to ecosystem provider 342 by payment network 314, and/or provided to one or more of application providers 338, 339 and 340 by ecosystem provider 342
  • a user may select at least a portion of data provided to ecosystem provider 342 by payment network 314, and select at least a portion of data to be shared with the one or more of application providers 338, 339 and 340.
  • a customer may select (e.g., via one or more button presses on a powered card and/or device card) an application to be associated to the transaction. Based on the selection, one or more additional actions may be taken besides the processing of the transaction by payment network 314. For example, a user may press a button on a powered card (e.g., transaction card 333).
  • a payment message e.g., a magnetic stripe message reflecting the button that was pressed may be communicated to merchant terminal 318.
  • Merchant terminal 318 may communicate a data string including the payment message and transaction information to payment network 314 via merchant acquirer 317.
  • Payment network 314 may receive the data string.
  • the data string may include a directive instructing payment network 314 to share data with ecosystem provider 342.
  • payment network 314 may share data with ecosystem provider 342 upon receiving the data string and recognizing, based on at least a portion of the data string (e.g., an account number), that data is to be shared.
  • Payment network 314 may cause the same or a different data string to be communicated from payment network 314 (e.g., from a processor within payment network 314) to ecosystem provider 342.
  • an issuer and/or a processor of an issuer may receive data and communicate at least a portion of the data and/or different data based on the received data to ecosystem provider 342.
  • a processor of issuer 320 may parse a data string received from merchant terminal 318 (e.g., via payment network 314) that includes a particular BIN number, may convert the data string into a different format and may forward the converted data string to ecosystem provider 342.
  • a processor of issuer 320 may parse a data string received from merchant terminal 318 (e.g., via payment network 314) that includes a particular BIN number, may convert the data string into a different format and may forward the converted data string to ecosystem provider 342.
  • Ecosystem provider 342 may receive the data string and compare user information (e.g., payment account number and/or payment account holder's name) that may be included within the data string to a user database to obtain a customer ID (e.g., a customer token) associated with the user information.
  • user information e.g., payment account number and/or payment account holder's name
  • customer ID e.g., a customer token
  • sensitive information within the data string may be replaced with the customer ID to create a modified data string, and the sensitive information may be stored either locally within ecosystem provider 342 or remotely to ecosystem provider 342.
  • the modified data string may be communicated to a third party application (e.g., one or more of application providers 338, 339 and 340) via, for example, IP Network 312.
  • ecosystem provider 342 may receive the data string.
  • the data string may be populated with information that may be indicative of which button was pressed on the powered card before being presented to merchant terminal 318.
  • ecosystem provider 342 may generate a third-party message with details that may be shared with a third-party application (e.g., one or more of application providers 338, 339 and 340).
  • the generated data string may include the customer ID and may be communicated to a third party application (e.g., one or more of application providers 338, 339 and 340) via, for example, IP Network 312.
  • a user may elect to share certain transaction information with one or more of application providers 338, 339 and 340 each time a certain button is pressed on the user's powered card before presentment to merchant terminal 318 for payment.
  • Such information may include, for example, merchant information (e.g., merchant's address), date/time information of a purchase, an amount of the purchase, a type of the purchase, and any other information (e.g., the customer ID associated with the customer's merchant account).
  • the various pieces of the transaction information may or may not be selected for sharing by the user via the user preferences.
  • a user may agree to share data during a registration process with an application provider (e.g., via an end user license agreement).
  • an application provider e.g., via an end user license agreement.
  • the sharable data may be automatically populated within a third-party message and communicated to an application provider via IP network 312.
  • the application provider Upon receipt of the third-party message, the application provider (e.g., one or more of application providers 338, 339 and 340) may enact a feature provided to a user (e.g., provide a coupon).
  • the application provider may initiate a second transaction (e.g., a piggyback transaction, a statement credit and/or the like).
  • the second transaction may be communicated to ecosystem provider 342 via IP network 312 (e.g., the internet) and processed by ecosystem provider 342 accordingly.
  • ecosystem provider 342 may determine whether a second transaction is permitted and/or forward information associated with the second transaction to another entity (e.g., issuer 320).
  • a GUI may, for example, be rendered onto a display of a user's card or other device (e.g., mobile device 302, user electronic device 345, transaction card 333 and/or contactless device 304).
  • the GUI may display indicia of one or more third-party applications (e.g., provided by one or more application providers 338, 339 and 340) along with summary and/or detailed information. Based upon information gleaned from the information concerning the applications, the user may be better informed as to which third-party applications he or she may wish to associate with his or her powered or non-powered card. Accordingly, the whimsical and festive nature of a user's experience with a GUI rendered by an electronic device may be further enhanced.
  • third-party applications e.g., provided by one or more application providers 338, 339 and 340
  • an application provider may be any entity.
  • ecosystem provider 342 may be an application provider in addition to providing an ecosystem.
  • an application provider may be a third-party application provider and ecosystem provider 342 may host the third party application (e.g., provide coupons).
  • Data sharing may be the same or different based on a particular configuration.
  • FIG. 36 shows device 400 (e.g., a card, a mobile telephonic device, a laptop computer, a desktop computer or an electronic tablet) that may include display 401.
  • Device 400 may include a processor that may render GUI 403 onto display 401.
  • GUI 403 may be an application manager.
  • a user may associate a payment method card (e.g., a powered physical card, non-powered physical card and/or device card) with third party service features within an ecosystem.
  • GUI 403 may be displayed on display 401, for example, a computer monitor, mobile phone touch screen and/or the like.
  • GUI 403 may be, for example, provided as an application for a device (e.g., a computer, a portable computing device and/or a mobile telephonic device) and/or retrieved information from a web browser.
  • An application manager may be provided, for example, on a remote facility and displayed via GUI 403 to allow a user to change the third party service features associated with a card.
  • An application manager may manage an ecosystem of applications and payment method cards, and the user may utilize GUI 403 to, for example, associate a particular feature to a particular payment method card at any time. The user may associate the selected feature with a card and/or a card button.
  • a default feature may be provided and/or that a number of features provided by a card issuer or other entity may be provided in addition to third party service features.
  • a card issuer may provide a card with a default of credit on one button and a default of decoupled debit on a second button. A user may press the first button to perform a credit transaction. A user may press the second button to perform a decoupled debit transaction.
  • GUI 403 may include tabs 405, information 411, virtual card 412, virtual indicia 413 and 414, slider 415, application identifiers 423 and 426, and selection options 428, 431, 432, 441-443 and 446.
  • Virtual card 412 may be provided as a representation of a user's physical and/or device card. A user may be provided with the ability to change between multiple different cards and configure the features associated with those multiple cards. Accordingly, virtual card 412 may be provided with indicia 413 in the configuration of, and indicative of, one button of a user's card, and virtual card 412 may be provided with indicia 414 in the configuration of, and indicative of, another button of a user's card. Indicia 413 and 414 may display the applications currently associated to each button (e.g., an application icon).
  • a slider 415 may be provided to indicate which of applications associated with a button may be a default application (e.g., for online, telephonic and/or non-powered card transactions). Accordingly, a user may, for example, view virtual card 412 in order to refresh the user's memory with respect to the features associated with the buttons on a user's physical and/or device card.
  • a list of applications may be provided on GUI 403. Each application may provide one or more third party service provider features.
  • a user may associate an application providing the feature to the card and/or card button(s). For example, selection 431 may associate application 423 to the button of a card associated with virtual button 413. Selection 432 may associate application 426 to the button of a card associated with virtual button 414. Accordingly, a user may change the features associated to a card by using GUI 403. In order to view the features provided by a particular application the user may, for example, select an "explore" button to view relevant information (e.g., selection 446).
  • the list of applications provided on GUI 403 may be, for example, all applications or a limited subset of all applications available to a user via an ecosystem provider.
  • tab 402 may be selected by a user (e.g., with a keyboard, mouse, touch sensitive screen and/or electronic pointer) to display an application manager home view.
  • a user may select a different tab.
  • tab 403 may be selected by a user to display a featured view including featured applications (e.g., applications-of-the-week).
  • Other tabs may sort applications by category, use and/or the like.
  • Selections 428 may be selections used to activate an application with respect to the user. Activation may include registration with a third party application, acceptance of an end users license agreement associated with the application, and/or the like. Activation may also include selecting a particular feature from among multiple features provided by the application. According to at least one example embodiment, some applications may not require activation (e.g., single feature, non-interactive applications).
  • a user may begin experiencing a selected feature by engaging in card transactions. For example, the user may press a card button associated with a desired feature during a card transaction.
  • a physical and/or device card (not shown) may communicate information indicative of a button that was pressed on the physical and/or device card, along with or separate from other payment data (e.g., an account number, security code, and other data). For example, information indicative of the button that was pressed may be included in discretionary data of a payment message.
  • a payment message may be, for example, one or more tracks of magnetic stripe data (e.g., communicated from a dynamic magnetic stripe communications device), an RFID message (e.g., a near field communication (NFC) message from a radio frequency antenna), and/or an exposed IC chip message (e.g., an EMV message) from an exposed IC chip.
  • magnetic stripe data e.g., communicated from a dynamic magnetic stripe communications device
  • an RFID message e.g., a near field communication (NFC) message from a radio frequency antenna
  • an exposed IC chip message e.g., an EMV message
  • the information indicative of which button was pressed may be passed to a card issuer and/or processor from a point-of-sale and any intermediary devices (e.g., a merchant acquirer processing server).
  • the information may be passed to a remote facility (e.g., a facility providing an application manager) such that the remote facility may determine the button that was pressed by a user.
  • This remote facility may, in turn, retrieve information associated with the third party feature (and/or a feature of a card issuer, processor, application manager provider, and/or any entity) and forward information to that feature provider such that the feature may be performed.
  • Information may additionally and/or alternatively be provided from the feature provider to the entity that provided the information indicative of the button that the user pressed.
  • a non-powered card information indicating that a button was pressed may not be available.
  • information indicative that a purchase was made may be provided to an application manager provider such that the application manager provider can initiate the desired feature for the non-powered card.
  • the feature may be a default feature, a selected feature (e.g., selected using an application manager) and/or a random feature.
  • features may be associated with different types of purchases. For example, one feature may be provided for a particular merchant type (e.g., a grocer's coupon) and another feature may be provided for a different merchant type (e.g., a clothing store coupon).
  • a particular merchant type e.g., a grocer's coupon
  • another feature may be provided for a different merchant type (e.g., a clothing store coupon).
  • Features may be associated with other characteristics of a purchase such as, for example, a purchase above a particular amount (e.g., at or above $100) and/or a purchase below a particular amount (e.g., below $100).
  • additional feature selections are not limited to non- powered cards and may be provided to, for example, users of powered cards and devices.
  • any feature and/or capability not requiring a powered device may be implemented with respect to a non-powered card and any feature and/or capability of a non-powered card may be implemented with respect to a powered card.
  • features and/or capabilities requiring a powered card may be implemented with respect to a non- powered card in various ways. For example, additional functionality may be provided at merchant terminals.
  • GUI 403 may be provided, for example, on a card issuer's and/or application manager provider's website. GUI 403 may be provided, for example, on a bill statement web page.
  • a user may utilize the application manager to manage application features when the user is logged into his/her account.
  • example embodiments described with respect to FIG. 4 may describe a GUI 403 used to make various selections and/or associations, persons skilled in the art will appreciate that other methods are possible. For example, selections may be made by phone, email and/or the like.
  • a third party service provider may utilize GUI 403 as part of a user's administration and/or experience of that third party service.
  • a user's profile page for a third party service may include GUI 403.
  • An application manager provider may provide web- code that retrieves GUI 403 from a remote facility managed by the application manager provider and/or other entity (e.g., issuer, merchant acquirer, payment network, merchant and/or the like).
  • Selection 441 may be utilized by a user to check for updates (e.g., confirm that a feature was changed and/or if any updates are present).
  • Selection 442 may be utilized to explain the functionality of a particular application feature.
  • Selection 443 may be utilized for additional selection options, for example, changing which card is displayed on an application manager.
  • a card may be provided with one button for a particular payment account (e.g., credit) and one button for a changeable feature. Accordingly, a user may, for example, only need to remember one feature associated with a card.
  • a credit account may include rewards, for example, points, cashback, and/or miles, from the card issuer. Accordingly, pushing the payment account button may earn the user such rewards.
  • Pushing the changeable feature button may, alternatively, for example, not earn the user such rewards and may instead initiate a changeable feature. In doing so, for example, the cost of providing a card may be reduced in that the cost of rewards for the card may be reduced.
  • a feature may include, for example, a feature from a third party application provider. The feature from the third party application provider may be, for example, a random reward (e.g., a random coupon).
  • Information 411 may, for example, identify the user and card number associated with virtual card 412 and a corresponding physical card.
  • tabs 405 may provide, for example, a history of purchases made by a user.
  • An application manager may provide indicia reflecting a user rating (e.g., star rating 447).
  • an ecosystem provider may be the same or different from an application manager provider, a remote facility and/or other entities.
  • One or more of the functions described herein as being performed by an application manager provider, and/or other entities, may be performed by the ecosystem provider.
  • an ecosystem provider may act as an application manager provider, application provider, issuer, merchant, third party service provider, payment network and/or the like to provide an end-to-end experience.
  • example embodiments contemplate the same, greater and/or fewer entities, and specific entities are described for purposes of explanation.
  • GUI 403 is provided for purposes of illustration only and may take various forms. For example, features may be associated to a card without buttons and/or a card may include the same, fewer and/or a greater number of buttons than depicted in FIG. 4.
  • FIG. 37 shows device 500 (e.g., a card, a mobile telephonic device, a laptop computer, a desktop computer or an electronic tablet) that may include display 501.
  • Device 500 may include a processor that may render GUI 502 onto display 501.
  • GUI 502 may be an application interface usable to manage a user's experience with an application.
  • GUI 502 may be used to, for example, configure application settings, receive information from an application provider, and/or communicate information to an application provider.
  • GUI 502 may include, for example, application screens 503, 507, 524, 542 and 550, tabs 505, 520, 540 and 545, information displays 510, 513, 523, 525, 527, 530 and 543, and selections 535 and 547.
  • Information display 503 may include, for example, information related to an application provider.
  • information display 503 may display the name and a brief history of the application provider.
  • Tab 505 may be used to display application screen 507 and may include a descriptor associated with application screen 507 (e.g., "How It Works"). Although example embodiments may be described with respect to tabs, persons skilled in the art will appreciate that tabs are used for purposes of explanation only. For example, redirection links may be provided to redirect a user to a configuration screen of an application provider. According to at least one example embodiment, tab 505 may be an information display without tab functionality.
  • Application screen 507 may be a configuration and/or informational screen for an application, and may display information explaining a feature provided by the application.
  • application screen 507 may include information indicating that a coupon will be provided to a user once the user meets or exceeds a performance metric.
  • a coupon may be, for example, a voucher entitling a user to a discount and/or a rebate.
  • the discount and/or rebate may be associated with a particular product, a purchase from a particular vendor and/or the like.
  • a performance metric may define, for example, a transactional event.
  • a performance metric may include a purchase with a card (e.g., a physical and/or device card), a sequence of purchases (e.g., ten purchases) with a card, and/or spending a target amount with a card. Any purchasing and/or non-purchasing transactional event is contemplated by example embodiments.
  • a performance metric may involve a rate of transactions (e.g., checkout 5 books from a library in 10 minutes), a pattern of transactions (e.g., purchase 10 different items from 10 different stores), a target transaction (e.g., purchase a particular item) and/or the like.
  • a rate of transactions e.g., checkout 5 books from a library in 10 minutes
  • a pattern of transactions e.g., purchase 10 different items from 10 different stores
  • a target transaction e.g., purchase a particular item
  • Application screen 507 may include information displays 510 and 513.
  • Information display 513 may include a representation of a type of reward, for example, an image representing a coupon.
  • Information display 510 may display a representation of a performance metric, for example, a monetary value and a payment method. Accordingly, for example, application screen 507 may indicate that a user of a payment method (e.g., a powered card) may receive a coupon and/or increase the value of a coupon each time the user spends an amount indicated in information display 510 using the payment method indicated in display 510.
  • a payment method e.g., a powered card
  • a coupon provided by an application provider may be selected in various ways. For example, a coupon may be randomly selected, may be selected by a user (e.g., from a list of coupons) and/or may be selected based on transactional information (e.g., data related to a purchase, a user purchase history and/or the like). The coupon may be selected prior to or after completion of the performance metric.
  • Each coupon may have a face value (e.g., a normal coupon value) and may be increased in value based on a value of the performance metric (e.g., a value to the application provider). For example, where a performance metric includes spending $100, $200 or $300, a value of the coupon may be 200% at the $100 level, 400% at the $200 level and 800% at the $300 level. A user may or may not select a level of the performance metric (not shown).
  • a face value e.g., a normal coupon value
  • a value of the coupon may be 200% at the $100 level, 400% at the $200 level and 800% at the $300 level.
  • a user may or may not select a level of the performance metric (not shown).
  • Tabs 520 may be used to display application screen 524.
  • Application screen 524 may include, for example, information displays 525, 527 and 530, and selections 535.
  • Information displays 525, 527 and 530 may, for example, display representations of redeemable coupons earned by a user.
  • Selection 535 may be used to change one or more of the coupon representations displayed in application screen 524 (e.g., to cycle through available coupons).
  • a user may, for example, select one of the representations to use the associated coupon for a specific purchase.
  • the coupon may be applied at any time the coupon is usable according to a user selection and/or by default (e.g., a coupon applied to the purchase of a specific product and/or in a specific store as a default).
  • Each of information displays 525, 527 and 530 may display information associated with a coupon in addition to, or alternatively to, the representation of the coupon.
  • the information may include a description of the value provided by the coupon, a description of added value to a base value of the coupon, an expiration date of the coupon and/or any other coupon related information (e.g., within the representation and/or beneath the representation).
  • each representation of a coupon may be a progress meter.
  • a user may build a coupon by selecting various information (e.g., base value, added value, expiration date and/or the like).
  • Tabs 540 may include one or more tabs used to display one or more application screens 542.
  • One of tabs 540 may be used to select an application screen including an information display listing earned coupons.
  • each of information displays 525, 527 and 530 may be selections representing categories of coupons.
  • a user may select information display 525 to display, for example, a list of earned coupons related to food in information display 543.
  • a user may select information display 527 to display, for example, a list of earned coupons related to small appliances in information display 543.
  • a user may select information display 530 to display, for example, a list of earned coupons related to prepared beverages in information display 543.
  • a list of earned coupons may also include, for example, unearned coupons.
  • the unearned coupons may be visually distinguishable from the earned coupons (e.g., a different color and/or shading).
  • Each displayed coupon may be, for example, a selection that may be used to begin earning the coupon, retrieve information associated with the coupon and/or the like.
  • more than one of information displays 525, 527 and 530 may be selected simultaneously.
  • One of tabs 540 may be selected to display a redemption history in information display 543.
  • a redemption history may, for example, display a purchase description and an amount saved.
  • one of tabs 540 may be selected to display a transaction history.
  • a transaction history may include, for example, information indicating a type of transaction (e.g., purchase), an amount spent, a date of the transaction and/or line items indicating that one or more coupons have been earned in relation to the transaction.
  • Tab 545 may selected to display application screen 550.
  • Application screen 550 may include selection 547.
  • a user (having met a performance metric) may activate an earned coupon.
  • a user may select a coupon from among multiple, available coupons and then press selection 547 to render the selected coupon usable.
  • the application provider may randomly select a coupon earned by the user and the user may press selection 547 to render the randomly determined coupon usable.
  • Selection 547 may include an information display (e.g., "$40 spent, press to redeem for coupon").
  • selection 547 may not be included and a coupon may be automatically activated by the application provider (e.g., based on user settings).
  • a user may be notified by an application provider when a coupon is earned and/or additional value is added to the coupon.
  • the application provider may utilize user submitted notification settings to notify the user.
  • a user may activate a coupon for a particular purchase and/or for any purchase (e.g., to be used when applicable).
  • the user may initiate a purchase using a payment method (e.g., powered card) and an activated coupon may be associated to the purchase (e.g., manually and/or automatically associated to the purchase).
  • a payment method e.g., powered card
  • an activated coupon may be associated to the purchase (e.g., manually and/or automatically associated to the purchase).
  • an application provider may receive transactional data indicating a type of product and/or a location of a purchase, search a list of coupons earned by a user and associate any applicable coupons to the purchase based on the transactional data.
  • value may be provided to the user (e.g., via a statement credit), for example, immediately, at authorization, at settlement and/or in a number of days.
  • the application provider may attach the coupon and/or a number associated with the coupon, for example, to an email.
  • a user may print the coupon and/or use number associated with the coupon (e.g., for an internet purchase).
  • a user may be notified of a reward or receive a reward via email, telephonic data transfer (e.g., text messaging), telegram and/or the like.
  • no notification may be provided and/or a user may be required to retrieve a coupon (e.g., via a GUI).
  • a coupon may be transmitted to a user's powered card and the powered card may be operable to display a barcode usable at, for example, a retail establishment.
  • a selection may be included to activate functionality by which outright purchases of a coupon and/or contributions towards a coupon may be made (not shown). Purchases and/or contributions may be made using, for example, piggyback charges, third party charges, direct purchases and/or the like.
  • a piggyback charge may be a statement debit (charge) added to a user statement, for example, for each purchase using a card and/or a device card.
  • a user may select an amount and/or frequency of the piggyback charge using, for example, GUI 502 (not shown).
  • GUI 502 not shown.
  • a user may earn a coupon and/or increase the value of a coupon for each piggy back charge.
  • a third party charge may be a monetary value provided by an application provider, for example, upon a user meeting an incentive performance metric in addition or alternatively to using the payment method (e.g., making purchases at a specific store and/or buying a specific product).
  • a direct purchase may be a partial or complete purchase of a feature by a user that is not attached to any other purchase.
  • a vendor may provide functionality by which a user may swipe a card and/or otherwise communicate data of a card to partially or wholly purchase a coupon without also purchasing any item from the vendor.
  • GUI 502 may include a blank information display (not shown).
  • a feature provider may provide 'drag-and-drop' coupon icons (e.g., on a feature provider website) representing the reward.
  • a user may drag the icon onto GUI 502 and GUI 502 may be automatically modified to include the coupon.
  • the icon transfer may include feature provider information, for example, information invisible to a user that may be used by an application.
  • the coupon provider may provide special incentives for a limited time (e.g., Black Friday), as a customer acquisition tool, as a customer retention tool, and/or the like.
  • GUI 502 may display a configurable coupon application.
  • a user may select from coupons provided by different retail outlets. The user may drag an icon from a webpage of a particular retail outlet onto the configurable application. The user may drag an icon from a webpage of a different retail outlet onto the configurable application. Both icons may appear on the configurable application. Accordingly, an application may not be limited to a specific retailer and/or coupon provider, and may enhance the whimsical and festive nature of a feature provided to a user.
  • An application accessed using GUI 502 may include configurable functionality to improve a user experience. For example, a representation of each coupon earned by the user may be publically and/or privately displayed when earned (and/or a progression display may be updated). For example, coupon information may be displayed on a user's social networking page, on a physical display at chosen location and/or the like.
  • an application provider and/or an application of an application provider may be associated to the user during, for example, an activation process. A user requesting access to an application may be prompted for information. The information may include, for example, security credentials used to access a social networking site associated with the user.
  • Selections may, for example, activate an additional and/or alternative feature.
  • a selection (not shown) may be used to pay an amount corresponding to completion of the performance metric displayed in information display 510.
  • the amount may be, for example, immediately charged via GUI 502 and/or may be attached as a piggyback charge to a purchase (e.g., a next purchase using a card and/or a device card). Accordingly, a user may take advantage of limited time offers even where the user does not expect to complete a performance metric within the limited time. The whimsical and festive nature of a coupon application may therefore be enhanced.
  • FIG. 38 shows process flow chart 600.
  • An application provider may receive user configuration selections (e.g., as in step 610) and transactional data from, for example, an application manager provider (e.g., as in step 620). The application provider may associate the transactional data with a user and determine if a performance metric has been completed (e.g., as in step 630). If a performance metric has not been completed, the application provider may update one or more information displays based on the received transactional data (e.g., as in step 640). If a performance metric has been completed, the application provider may display a completion message to a user and update one or more information displays (e.g., as in step 650). A value (e.g., coupon) may be transmitted to, for example, the payment method user (e.g., as in step 660).
  • a value e.g., coupon
  • a coupon provider may receive a user feature selection.
  • the coupon provider may receive transactional information, for example, information indicative of a feature selected by a user (e.g., via a telephone device card, powered card and/or the like) and transactional information related to a payment card (e.g., a number of transactions performed by the user with the payment card, an amount spent and/or the like).
  • transactional information for example, information indicative of a feature selected by a user (e.g., via a telephone device card, powered card and/or the like) and transactional information related to a payment card (e.g., a number of transactions performed by the user with the payment card, an amount spent and/or the like).
  • the coupon provider may determine if a performance metric has been completed.
  • a performance metric may include ten user purchases using a powered credit card.
  • a progression display (e.g., a progress meter) may be updated (e.g., if applicable). If the transactional metric has been met, an email may be sent notifying the user that the coupon has been earned. One or more progression displays may be updated and the coupon may be communicated to the user. According to at least one example embodiment, the notification and coupon may be communicated to the user in the same email message.
  • a coupon code may be communicated to the user.
  • a user may be notified that a coupon code and/or a coupon is available electronically (e.g., accessed from an application manager).
  • FIG. 39 shows device 700 (e.g., a card, a mobile telephonic device, a laptop computer, a desktop computer and/or an electronic tablet) that may include display 701.
  • Device 700 may include a processor that may render GUI 702 onto display 701.
  • GUI 702 may be an application interface usable to manage a user's experience with an application.
  • GUI 702 may be used to configure application settings, receive information from an application provider, communicate information to an application provider and/or the like.
  • GUI 702 may include, for example, tabs 703, 718, 730 and 763, application screens 707, 723, 752 and 773, information displays 710, 713, 715, 727, 733, 737, 740, 743, 753, 755, 757 and 760, progress meter 725, entry fields 767 and 775, and selections 765, 770 and 777.
  • Tab 703 may be used to display application screen 707 and may include a descriptor associated with application screen 707 (e.g., "How It Works"). Upon selecting tab 703, application screen 707 may be displayed to a user.
  • Application screen 707 may be a configuration screen for an application and may include information explaining features provided by the application.
  • application screen 705 may display different configurable, selectable features, along with explanatory information associated with each feature.
  • application screen may not be a configuration screen and may be an information screen.
  • a feature may not be configurable and/or selectable (e.g., a set feature) and static feature information may be displayed.
  • a feature provided by an application may provide a user selected reward once a user meets or exceeds a performance metric.
  • a feature provided by an application may provide a random reward from a collection of rewards once a user meets or exceeds a performance metric.
  • the reward may be provided by the application provider upon a user meeting or exceeding the performance metric.
  • An example of a performance metric may include a user completing one or more purchases meeting or exceeding a monetary value using a payment card.
  • a feature provided by an application provider may be represented by, for example, information displays 710, 713 and 715.
  • information display 713 may display an image representing a collection of different rewards.
  • Information display 710 may display information associated with a performance metric.
  • the performance metric may be, as one example, a transactional based performance metric represented by an image of a payment card and a monetary value.
  • Information display 715 may include information associated with the performance metric and/or the collection of rewards. For example, information display 715 may notify a user that shopping at a particular store will earn additional rewards, and/or notify a user as to the odds of winning any one of the rewards from the collection of rewards.
  • application screen 707 may include information describing that a user may earn one random reward from a collection of rewards upon spending at least a monetary value (e.g., $6,000) using a payment method (e.g., a smartphone payment card). If the payment method is used to make purchases from a store (e.g., a particular store associated with the application) the amount spent in order to earn the reward may be reduced (e.g., earn a reward twice as fast).
  • a payment method e.g., a smartphone payment card
  • application screen 723 may be displayed to a user.
  • Application screen 723 may include progress meter 725 and information display 727.
  • Progress meter 725 may indicate user progress towards completing a performance metric.
  • Progress meter 725 may be any type of progress meter.
  • a progress meter may be represented as a thermometer with a temperature scale replaced by a monetary scale (e.g., $0- $6,000).
  • a user may gauge progress towards a reward.
  • Information display 727 may, for example, display an exact amount spent towards earning the reward.
  • a type of progress meter 725 is not limited.
  • an application provider may be an actress named 'Dynama Lemon.'
  • the application provider may display a representation of a lemon.
  • the representation may be, for example, a black and white outline.
  • the representation of the lemon may be progressively colored-in to demonstrate progress.
  • application screen 752 may be displayed to a user.
  • Application screen 752 may provide details with respect to the representation of the collection of rewards displayed in information display 713, and may include, for example, information displays 737, 740, 743, 753, 755, 757 and 760.
  • Information displays 737, 740 and 743 may each display a representation of, for example, a coupon (e.g., different coupons) and information related to each coupon (e.g., an additional value associated with a coupon when the payment method is used to buy specific products).
  • Information displays 753, 755, 757 and 760 may each display a representation of a tangible item and a description of the tangible item.
  • the coupons and tangible items may be a collection of rewards from which a reward may be randomly awarded to the payment method user upon completion of the performance metric.
  • Selection 765 may be a redemption button that may be used upon completion of the performance metric to receive the random reward.
  • a user may change, for example, notification settings before using selection 765.
  • a user may be awarded a random reward from among coupons and tangible items.
  • coupons may include a coupon providing 5% off purchases of a product, $50 off purchases of $500 or more, 15% off purchases from a specific store and/or retailer, and/or the like.
  • tangible items may include a makeup kit, a purse, nail polish remover, a ring and/or the like. Each item may be, for example, exclusively available to users of the payment method.
  • Tab 763 may be associated to notification settings. For example, tab 763 may be selected by a user to display entry fields 767 and 775, and selections 770 and 777. Entry fields 767 and 775 may be used by a user to enter information related to the type of notification (e.g., an email address and/or a text message number). Selections 770 and 777 may be used to submit the information entered into entry fields 767 and 775, respectively.
  • information related to the type of notification e.g., an email address and/or a text message number.
  • Selections 770 and 777 may be used to submit the information entered into entry fields 767 and 775, respectively.
  • a user may be notified by the application provider when a reward is earned.
  • the application provider may utilize user submitted notification settings to notify the user. For example, a user may submit an email address using entry field 767 and selection 770. As another example, a user may submit a number (e.g., a telephone number for text messaging) using entry fields 775 and selection 777.
  • a notification email and/or text message may be sent to the email and/or number when a reward is earned.
  • the email and/or text message may include a message indicating that a reward has been earned and that a redemption code usable to retrieve the reward is available.
  • the application provider may attach the redemption code and/or reward to the notification (e.g., embedded in the email).
  • electronic rewards may be downloaded by clicking, for example, an information display associated with the earned reward (e.g., using an application manager).
  • example embodiments are described with respect to email and/or text messaging, persons of ordinary skill in possession of example embodiments will appreciate that many different notification methods may be used (e.g., telephonic, text messaging, telegram and/or the like). According to at least one example embodiment, no notification may be provided. According to other example embodiments, a user may provide a physical address at which to receive notifications and tangible rewards.
  • a user may submit multiple addresses (e.g., one or more email addresses, one or more telephone numbers, and/or one or more physical addresses) and select one of the addresses prior to redemption such that each reward redemption may result in a different notification or fulfillment (e.g., different rewards and/or notifications may be sent to different addresses at the whim of the user).
  • addresses e.g., one or more email addresses, one or more telephone numbers, and/or one or more physical addresses
  • example embodiments described in relation to FIG. 7 may include performance metrics based on a monetary value, various other performance metrics are within the scope of example embodiments (e.g., number of transactions, type of transactions, a user acting as a merchant using a particular merchant service and/or the like).
  • FIG. 8 shows device 800 (e.g., a card, a mobile telephonic device, a laptop computer, a desktop computer or an electronic tablet) that may include display 801.
  • Device 800 may include a processor that may render GUI 802 onto display 801.
  • GUI 802 may be an application interface usable to manage a user's experience with an application.
  • GUI 802 may be used to configure application settings, receive information from an application provider, communicate information to an application provider and/or the like.
  • GUI 802 may include, for example, tab 805, application screen 807, information displays 810, 820, 830 and 840, and selection 850.
  • Tab 805 may be used to display application screen 807 and may include a descriptor associated with application screen 807 (e.g., "Scratch Off"). Upon selecting tab 805, application screen 807 may be displayed to a user. Application screen 807 may be an interactive selection screen for an application.
  • a descriptor associated with application screen 807 e.g., "Scratch Off”
  • a feature provided by an application may provide a user an opportunity to select one reward from among multiple, hidden rewards. For example, a user may be presented with multiple representations of a logo (e.g., an application provider logo) in information displays 810-840. The user may be provided the opportunity to select one of information displays 810- 840 to unveil a reward. For example, a user may select information display 820 to reveal that the user has won a coupon (e.g., 15% off of a purchase).
  • a logo e.g., an application provider logo
  • a user may select two or more of information displays 810-840 and receive a reward associated with each selection.
  • multiple performance metrics may be available to the user.
  • a value e.g., cost to the user and/or value provided to the application provider
  • a different number of selection may be made (e.g., one selection for $50 in spends, two selections for $100 in spends, etc.).
  • an application provider may receive a monetary value from, for example, an ecosystem provider, an issuer, a merchant and/or a payment network in exchange for providing a reward to a user.
  • the monetary value may be, for example, a number of basis points (1/100 of a percentage point) related to a transaction.
  • an application provider may not receive a monetary value and/or may provide value.
  • the application provider may receive value, for example, via customer acquisition, retention of customers, marketing (e.g., visibility within an ecosystem) and/or the like.
  • a value provided via a coupon may be greater than a monetary value provided to a coupon provider.
  • a difference in value may be offset by other factors (e.g., high value coupons where 90% of the coupons are expected to expire prior to use).
  • a performance metric may be based on transactional processing.
  • Transactional processing may include multiple stages.
  • a credit transaction may include authorization, batching, clearing and funding.
  • An application and/or feature provider may provide a reward to a user at one of the various stages of transaction processing (e.g., authorization).
  • a transaction may be reversed (e.g., a void or credit) after a user receives a reward based on the transaction. For example, a user may purchase an item, receive an electronic reward and then return the purchased item.
  • the application and/or feature provider may be notified by the application manager provider that a transaction has been reversed.
  • a application and/or feature provider may take action based on the notification, for example, provider may reclaim a coupon, invalidate a coupon code, remove user authorization to use an application and/or feature, establish a debit pool that must be reduced by future uses of the payment method before additional rewards may be earned and/or the like.
  • a reward may be granted to a user at a stage of transaction processing (e.g., authorization) but may not be available for use by the user until a different stage of processing (e.g., settlement).
  • a transaction is reversed (e.g., via a return, a charge-off and/or a charge-back) after being made available to the user the application and/or feature provider may take steps to remove a value associated with the coupon. Accordingly, if a card is used fraudulently (e.g., a stolen card), rewards may be disassociated with a reward system when the purchases are charged-off as a result of the fraudulent spend.
  • a card is used fraudulently (e.g., a stolen card)
  • rewards may be disassociated with a reward system when the purchases are charged-off as a result of the fraudulent spend.
  • FIG. 40 shows process flow chart 900.
  • a rewards provider may utilize an application to configure rewards (e.g., for a rewards or loyalty program).
  • a computing device e.g., a server
  • reward description details may be defined (e.g., as in step 910).
  • a rewards provider may select a type of reward, enter a name for the reward, provide a brief description of the reward and upload an image to represent the reward.
  • the reward type may be, for example, a coupon, an item, a virtual item, cashback, points, miles, entry into a lottery, and/or any other type of reward.
  • the GUI may display further options tailored to the type of reward.
  • a rewards provider may define reward execution details (e.g., as in step 920). For example, a coupon provider may determine the type of coupon that will be provided to users by selecting various options. The options may determine, for example, whether or not the coupon will be based on a purchase amount or a purchased product, and the type of discount or rebate to be applied. If the coupon will be based on a purchase amount, the type of discount or rebate may include, for example, a percentage or value based discount. If the coupon will be based on a purchased product, the type of discount or rebate may include, for example, a percentage discount, a value based discount or a replace value.
  • a rewards provider may set distribution limits for the rewards program (e.g., as in step 930).
  • the distribution limits may define the financial liability that may be incurred by the rewards provider.
  • a coupon provider may limit the number of coupons that are distributed and/or the maximum value of the coupons (e.g., the value either individually or in aggregate).
  • a rewards provider may set an overall distribution limit of 1000 coupons and a per customer distribution limit of 5 coupons.
  • a rewards provider may define reward execution requirements (e.g., as in step 940).
  • Reward execution requirements may, for example, describe the circumstances under which a coupon is redeemable.
  • coupons redemption may be limited to online purchases or store purchases, or permitted for both store purchases and online purchases.
  • in-store redemption is permitted, the redemption may be limited to a particular store, a set of particular stores, and/or one or more geographical areas (e.g., by zip code, province/state and/or country).
  • Information that may be entered into a GUI by a rewards provider may include, for example, one or more store ID's, store names, zip codes, province/state information and/or country codes.
  • reward redemption may be limited to one or more retailers (e.g., Dynamo Sporting Goods), to one or more types of retailers (e.g., sporting goods), by maximum and/or minimum purchase thresholds (e.g., purchase amount thresholds), by duration (e.g., a range of dates), by date (e.g., specific days), by time (e.g., specific hours), and/or by product and/or product group (e.g., to one or more SKU groups).
  • retailers e.g., Dynamo Sporting Goods
  • types of retailers e.g., sporting goods
  • maximum and/or minimum purchase thresholds e.g., purchase amount thresholds
  • duration e.g., a range of dates
  • date e.g., specific days
  • time e.g., specific hours
  • product and/or product group e.g., to one or more SKU groups
  • coupon redemption may be circumscribed by, for example, location, commercial relationships, cooperative interests, and/or logistical considerations.
  • a retailer may increase traffic through stores at historically underperforming times, days or months, reduce percentage reduction liability that may occur for higher value purchases, and restrict coupons to particular products, manufacturers or types of manufacturers.
  • a retailer with knowledge of customer loading patterns within its stores may limit coupon redemption to particular stores at particular times on particular dates to level workload, control local traffic, synergize with staffing levels and/or increase loading at underperforming stores or regions.
  • a rewards provider may define reward usability and compatibility (e.g., as in step 950).
  • a retailer may define how coupons are used together (coupon usability), define the types of payment methods that are usable during a qualifying purchase (purchase types), and/or define the transferability of the coupons (user restrictions).
  • defining coupon usability may include selecting whether coupons are usable with all other coupons, with specific coupons or only by themselves.
  • Defining purchase types may include selecting payment methods with which a coupon may be used, for example, all payment methods, specific branded payment methods (e.g., store loyalty credit card), cash, prepaid cash, payment methods supported by specific payment networks (e.g., Visa, MasterCard, Discover and/or American Express) and/or the like.
  • Defining user restrictions may include restricting redemption to a designated user or designated users (e.g., the user to whom the coupon was sent) or permitting redemption by any user (e.g., a transferable coupon).
  • process flow chart 900 includes arrows, the arrows are not limitations of order. Persons of ordinary skill in the art will appreciate that some or all of the described activities may be completed sequentially, in a different order or simultaneously. Although process flow chart 900 may be described above with respect to coupons, persons of ordinary skill in possession of example embodiments will understand the described process to be broadly applicable to various types of rewards. Persons of ordinary skill will understand that whether a process is described with respect to selection or entry, a selection may be implemented with an entry, an entry with a selection, and other possibilities exist (e.g., pulling SKUs from a database or other file).
  • FIG. 41 shows process flow chart 1000.
  • a rewards provider may utilize an application to configure a loyalty program.
  • a computing device e.g., a server
  • a reward provider may define a description of a loyalty program (e.g., as in step 1010).
  • a rewards provider may select a program type, enter a name for the loyalty program, provide a brief description of the loyalty program and identify one or more rewards provided by the loyalty program.
  • the program type may be, for example, a predefined type of loyalty program. Once a reward type is selected, the GUI may display further options tailored to the type of loyalty program.
  • a rewards provider may define one or more reward distribution criteria (e.g., as in step 1020).
  • a loyalty program may provide a reward based on a monetary value spent (e.g., number of dollars), a number of visits (in-store and/or online), a number of particular items purchased and/or a number of purchases.
  • a selection to base a loyalty program on monetary value may include entering an amount of the monetary value at which a reward may be provided.
  • a selection to base a loyalty program on a number of visits may include entering the number of visits before a reward may be provided, and may include entering a number of consecutive days on which the visits must occur (e.g., a date range or a number).
  • a selection to base a loyalty program on a number of purchased items may include entering one or more item types, one or more stock keeping units (SKU), and/or entering a number representing the number of items to be purchased before a reward may be provided.
  • a selection to base a loyalty program on a number of purchases may include entering a number representing the number of purchases before a reward may be provided, and may include entering a minimum spend amount per purchase.
  • a rewards provider may set a rewards distribution criteria period for the loyalty program (e.g., as in step 1030).
  • the distribution criteria period may specify a time period in which the loyalty program is deemed to be active and rewards may be earned.
  • a rewards provider may select an option to provide rewards from program inception or enter a date range.
  • a rewards provider may apply a retroactive time period such that historical data may be used to determine whether a reward was earned (e.g., prior to inception of the program).
  • a rewards provider may set program earning time constraints with respect to the loyalty program (e.g., as in step 1040). For example, reward earning may be limited such to only specific days, and/or specific days and times.
  • a loyalty program may be implemented to provide loyalty rewards for customers shopping on Black Friday (e.g., November 28, 2014) during non-peak hours.
  • a rewards provider may define program run limits (e.g., as in step 1050). For example, a rewards provider may select one or more options that may include running a loyalty program until start and end dates have been met (e.g., a date range), a particular amount of rewards have been generated, a particular amount of rewards have been redeemed, a particular amount of value has been generated and/or a particular amount of value has been redeemed.
  • start and end dates e.g., a date range
  • a rewards provider may define program distribution criteria (e.g., as in step 1060). For example, a rewards provider may elect to distribute rewards only to a particular segment of a customer or consumer base. Rewards may be distributed based on psychographics, for example, any personality trait, value, attitude, interest, and/or lifestyle choice (e.g., "gamers,” “savers,” “sportsters,” and/or “child conscience parents”). Award distribution may be based on, for example, gender, age, income and/or products (e.g., one or more SKUs). For example, coupons for geriatric feminine products may be distributed to female consumers by selecting gender and age as a basis for distribution, and entering product SKUs corresponding to the geriatric feminine products.
  • process flow chart 1000 includes arrows, the arrows are not limitations of order. Persons of ordinary skill in the art will appreciate that some or all of the described activities may be completed sequentially, in a different order or simultaneously. Although process flow chart 1000 may be described above with respect to coupons, persons of ordinary skill in possession of example embodiments will understand the described process to be broadly applicable to various types of rewards. Persons of ordinary skill will understand that whether a process is described with respect to selection or entry, a selection may be implemented with an entry, an entry with a selection, and other possibilities exist (e.g., pulling SKUs from a database or other file).
  • FIG. 42 shows process flow charts 1100 and 1150.
  • a rewards provider may utilize an application to test a loyalty and/or rewards program by providing rewards to all, or one or more segments of, identified consumers (e.g., customers) and monitoring the effect of the reward.
  • the effect of the reward may be determined via test result data in multiple ways and may depend on the reward. For example, if a coupon is offered as a reward, transaction data and/or coupon-use data may be monitored to determine if the coupon resulted in a change in consumer behavior. The data may be collected at one stage of transaction processing (e.g., authorization, settlement, and/or the like), each stage or any combination of stages.
  • transaction data and/or coupon-use data may be monitored to determine if the coupon resulted in a change in consumer behavior.
  • the data may be collected at one stage of transaction processing (e.g., authorization, settlement, and/or the like), each stage or any combination of stages.
  • test result data may include segment data from one or more segments receiving a coupon, from one or more segments not receiving a coupon and/or from one or more segments receiving a different coupon (multi-segment testing).
  • Test results may include data from a portion of a segment receiving a coupon and a portion of a segment not receiving a coupon (in-segment testing).
  • Test result data may include data from an entire consumer base (global testing).
  • segment data e.g., in-segment and/or multi- segment data
  • before-and-after data may be compared (in- segment, multi-segment and/or global) using collected and historical data.
  • a computing device may display an interactive GUI that is usable to describe and/or define test and distribution criteria used in program testing (e.g., as in step 1110).
  • a rewards provider may select a loyalty or rewards program for testing, enter a name of the test, enter a brief description, enter a number of rewards to generate, and/or select a percentage or number of consumers (e.g., customers and/or non-customers) to receive the generated rewards.
  • the selected percentage or number may be applied to an entire consumer base (e.g., 100% where no segments are defined), to segments of a consumer base (e.g., x% where multiple segments are defined) and/or to a single segment of a consumer base (e.g., x% where a single segment is defined).
  • Individual segments may be, for example, defined by distribution criteria.
  • a rewards provider may define one or more segments to be used in program testing be selecting or entering distribution criteria (e.g., as in step 1120).
  • a segment may be based on, for example, psychographics.
  • Psychographics may include any personality trait, value, attitude, interest, and/or lifestyle choice (e.g., "gamers,” “savers,” “sportsters,” and/or “child conscience parents”).
  • a segment may be based on characteristics or goods, for example, gender, age, income and/or products (e.g., one or more SKUs). Consumer psychographics and characteristics may be entered by a user and/or determined from transactional data.
  • test may be initiated (e.g., as in step 1130).
  • the coupons may be distributed and data collection begun (e.g., via routing of transaction messages to a remote facility or other entity).
  • data may be analyzed and results may be provided.
  • Graphs may be displayed to summarize the test results.
  • a test may be repeated one or more times and graphical data may be continuously updated. Repetition may provide temporal or event based effect information (e.g., seasonal habits or the effects of weather).
  • tests may be triggered based on events to determine their impact on consumer habits (e.g., geographic testing triggered by a catastrophe).
  • a computing device may display an interactive GUI that is usable to simulate a loyalty program or rewards program.
  • a rewards program may be built and simulated to ensure that the rewards program functions according to the reward provider's intended design.
  • a rewards provider may select a loyalty or rewards program (e.g., as in step 1160).
  • the reward program may be selected using the reward description (e.g., "incentive coupon").
  • the program may be, for example, selected from a list of programs. If the coupon includes a barcode, the type of barcode may be selected.
  • a coupon simulation type may be selected.
  • a coupon simulation type may be, for example, a valid coupon or a test coupon.
  • An address e.g., email address) of a user and a mail server identification may be entered.
  • the program may be simulated (e.g., as in step 1170) by, for example, selecting to send one or more test emails (e.g., in a case where coupons are distributed by email), or by entering condition settings and selecting to simulate the program based on the condition settings.
  • a condition may include, for example, maximum liability.
  • the simulation may determine, based on the rewards program, the maximum liability where the maximum number of coupons are distributed and used. Alternatively, percentage of use assumptions and the like may be entered to determine a resulting liability based on the assumptions.
  • conditions may include any parameter used to determine the result of a defined rewards or loyalty program.
  • process flow charts 1100 and 1150 include arrows, the arrows are not limitations of order. Persons of ordinary skill in the art will appreciate that some or all of the described activities may be completed sequentially, in a different order or simultaneously. Although process flow charts 1100 and 1150 may be described above with respect to coupons, persons of ordinary skill in possession of example embodiments will understand the described process to be broadly applicable to various types of rewards. Persons of ordinary skill will understand that whether a process is described with respect to selection or entry, a selection may be implemented with an entry, an entry with a selection, and other possibilities exist (e.g., pulling SKUs from a database or other file).
  • FIG. 12 shows process flow charts 1200 and 1250.
  • Process flow chart 1200 may provide an example of the implementation of a rewards program and process flow chart 1250 may provide an example of the implementation of a loyalty program.
  • a computing device may display an interactive GUI usable to define a rewards program (e.g., as in step 1205).
  • a remote facility may receive rewards program configurations (e.g., as in step 1210) from, for example, a third party provider (e.g., a retailer). Based on the defined program, the remote facility may distribute rewards according to the program definition. For example, the remote facility may distribute coupons to all customers within a demographic (e.g., globally, by segment, by partial segment and/or the like).
  • the rewards may be distributed physically (e.g., by mail, courier, in-store and/or the like) and/or non-physically (e.g., via electronic mail, telephonically, SMS messaging, television, social networking and/or the like).
  • a server of a remote facility may receive or pull data from a server of a third party provider, and based on the data distribute coupons to consumers via electronic mail.
  • the remote facility may receive reward redemption information (e.g., as in step 1220).
  • the third party provider may communicate coupon redemption information to a remote facility (e.g., an ecosystem provider), and/or the remote facility may receive transactional data from one or more network entities in a transactional flow.
  • the transactional data may include, as one example, an authorization message.
  • the reward redemption information may include, for example, coupon identification information, user information, location information, product information, establishment information (e.g., store ID), purchase price information, and/or any other transactional data.
  • the remote facility may determine if the coupon is valid based on the reward redemption information and a rewards program.
  • the remote facility may, for example, determine if the coupon is recognized as active for a rewards program, and if the coupon redemption meets the requirements of a rewards program.
  • a rewards program may provide a discount that is only valid at a particular store, on a particular date and for a particular user.
  • the remote facility may receive an authorization message that includes identification of a coupon and determine if the coupon is active for any rewards program. If the coupon is active, the remote facility may compare received transactional information against the requirements for the rewards program.
  • the remote facility may provide validation information (e.g., as in step 1225) to a third party provider, a merchant terminal, an issuer, and/or other entity. For example, if the coupon is active and the transaction complies with the requirements of a rewards program, the remote facility may communicate information indicating that the discount or rebate may be applied to the transaction. If the coupon does not meet one or more criteria for redemption, the remote facility may indicate that the discount or rebate should not be applied to the transaction.
  • validation may occur after a purchase, for example, based on settlement.
  • a computing device e.g., a server
  • a remote facility may receive loyalty program configurations (e.g., as in step 1260) from, for example, a third party provider (e.g., a coupon provider).
  • a third party provider e.g., a coupon provider
  • the remote facility may receive transaction data. Based on the transaction data, historical data and a loyalty program definition, the remote facility may determine loyalty program applicability and performance metric status (e.g., as in step 1265).
  • a server of a remote facility may receive or pull data from a server of a third party provider, or receive transactional messages from an entity within a purchase flow (e.g., as described with respect to FIG. 3).
  • the transactional data may evaluated to determine if a loyalty program applies.
  • a loyalty program may award a coupon to users of a particular loyalty credit card that fall within a particular demographic.
  • the remote facility may evaluate the transactional data to determine if a performance metric has been met.
  • the performance metric may include completing 10 purchases of a particular product using the loyalty credit card.
  • the historical data may indicate that the user has previously purchased the particular product 9 times and the current purchase completes the performance metric.
  • a reward may be distributed as defined in the loyalty program (e.g., as in step 1270). If the performance metric has been met, a discount may be automatically applied to the transaction by communicating a message (e.g., to a point-of-sale device) and/or a coupon may be communicated to the user.
  • a message e.g., to a point-of-sale device
  • the remote facility may receive reward redemption information (e.g., as in step 1275) upon use of the coupon.
  • the third party provider may communicate coupon redemption information to the remote facility, and/or the remote facility may receive transactional data including reward redemption information from one or more network entities in a transactional flow.
  • the transactional data may include, as one example, an authorization message.
  • the reward redemption information may include, for example, coupon identification information, user information, location information, product information, establishment information (e.g., store ID), purchase price information, and/or any other transactional data.
  • the remote facility may determine if the coupon is valid based on the reward redemption information and the loyalty program definition.
  • the remote facility may, for example, determine if the coupon is recognized as active for a loyalty program, and if the coupon redemption meets the requirements of the loyalty program.
  • the loyalty program may provide a discount or rebate that is only valid when used during specific hours in a particular country.
  • the remote facility may receive a message (e.g., a settlement message) that includes identification of a coupon and determine if the coupon is active for any loyalty program.
  • the remote facility may compare the received transactional information against the requirements for the rewards program. For example, the remote facility may determine if the coupon is being used during the specific hours and in the particular country, as required by the loyalty program. If the coupon is active and the requirements of the loyalty program are met, the coupon may be determined valid. Otherwise, the coupon may be determined invalid.
  • the remote facility may provide validation information (e.g., as in step 1280) to a third party provider, a merchant terminal, an issuer, and/or other entity. For example, if the coupon is valid, the remote facility may communicate information indicating that the discount or rebate may be applied to the transaction. If the coupon is not valid, the remote facility may indicate that the discount or rebate should not be applied to the transaction.
  • validation may occur, for example, at authorization (or any other stage of processing).
  • process flow charts 1200 and 1250 include arrows, the arrows are not limitations of order. Persons of ordinary skill in the art will appreciate that some or all of the described activities may be completed sequentially, in a different order or simultaneously.
  • process flow charts 1200 and 1250 may be described above with respect to coupons, persons of ordinary skill in possession of example embodiments will understand the described processes to be broadly applicable to various types of rewards. Persons of ordinary skill will understand that if a process is described with respect to selection or entry, a selection may be implemented with an entry, an entry with a selection, and other possibilities exist (e.g., pulling SKUs from a database or other file). According to example embodiments, cards, ecosystems, third party applications, testing, simulation and transaction flows may be included in the implementation of a reward or loyalty program.
  • Example embodiments described with respect to process flow charts 1200 and 1250 are not limiting of example embodiments, but serve as examples.
  • Various transactional flows and systems may be implemented in various ways (e.g., as described with respect to FIG. 3). Although specific entities may be used to describe example embodiments in relation to FIG. 12, various entities may perform one or more functions of other entities, and the particular entities used to describe
  • FIG. 12 are not limiting.
  • a value document may be used to generate demographic information to understand consumer behavior by providing, for example, incentives to purchase, reductions in the price of particular items, free samples, and/or the like.
  • a value document may provide free shipping, buy-one get-one, trade-in for redemption, a coupon for a first-time customer, free trial offer, launch offer, special event offer and/or free giveaway.
  • a value document may be, for example, a coupon providing $5.00 off a $10.00 purchase, and the coupon may be represented by a two or three dimensional barcode.
  • a price conscious consumer may, for example, present a coupon to check out at a merchant, and the merchant may retain the coupon and offer the consumer a loyalty card during the check-out process. Consumer acceptance of the loyalty card may be low.
  • a value system may issue an value identifier to influence consumer behavior for loyalty or advanced coupon features.
  • a value system may provide a multistage value account identifier which is individualized based on use of the multistage value account identifier.
  • the multistage value account identifier may be, for example, a single code (e.g., represented by a barcode).
  • the multistage value identifier may be associated to a multistage value account.
  • the multistage value account may or may not be associated with a particular user.
  • a multistage value account may be associated with a defined or undefined set of stages.
  • a stage may require, for example, a particular action (e.g., a purchase or a game move). For example, at a first visit to a retailer, a user may present a multistage value account identifier to receive $5.00 off a $10.00 purchase, and at a second visit receive $10.00 off a $20.00 purchase, and at a third visit receive $15.00 off a $20.00 purchase and at a fourth visit receive a free sandwich along with a message announcing that the user of the multistage value account identifier has achieved status and will be provided a card (e.g., gold status card) upon providing user information (e.g., a telephone number, email address, physical address and/or other information associated with the consumer).
  • a card e.g., gold status card
  • the card may, for example, represent a conventional loyalty program, specific privileges and/or expand the benefits provided by the multistage value system (e.g., with increasingly individualized customization based on information obtained from redemption associated with the stages of the multistage value account and/or based on user information).
  • User information may be requested via, for example, a retailer POS system, a method specified by the POS system, a receipt and/or an online purchase confirmation.
  • a user may receive an advertisement including a multistage value account identifier or method of obtaining a multistage account identifier, along with information indicating that upon achieving a particular stage the user is eligible for a status card upon submitting user information (e.g., to a website URL).
  • use of a multistage value account identifier may be conditioned on consent by the user for access to user information, for example, user information stored by a merchant, acquirer, issuer, processor, payment network, third party service provider, remote facility, device provider, mobile service provider and/or any other entity.
  • a multistage value system may be an implementation of an abbreviated (mini) loyalty program or an introductory loyalty program and a user may be seamlessly converted from the multistage value account to a value program.
  • a user may be converted to a loyalty card representing an extension of the multistage value system, or a different and/or traditional loyalty program. Consumer acceptance of the loyalty card may be increased and/or high as compared to conventional program offerings at checkout.
  • one or more stages of a multistage value account may expire. According to other example embodiments, no stage of a multistage value account expires. According to still other example embodiments, one or more stages of a multistage value account may include a change date after which a different value is offered to the consumer.
  • a consumer may be offered a choice of value from a pool at a first stage.
  • a choice may be presented to a user at one or more stages or every stage of a multistage account.
  • no choice is offered to the user.
  • Machine learning may be applied to determine the value or pool of values offered at one or more stages of a multistage value account based on, for example, previous value selections by a user, use of the multistage value account identifier (e.g., redemption data), information submitted by a user, demographic data and/or any other information relevant to individualizing value to a user of a multistage value account.
  • the multistage value account identifier e.g., redemption data
  • information submitted by a user e.g., demographic data and/or any other information relevant to individualizing value to a user of a multistage value account.
  • Artificial intelligence may, for example, provide a multistage value system subscriber segmentation including groupings or patterns within a customer base of the subscriber.
  • the multistage value system subscriber may be offered choices of values to be offered to a user at one or more stages based on segmentation.
  • a multistage value system subscriber may be, for example, a game company, issuer, processor, acquirer, payment network, merchant, property owner (e.g., mall owner or strip mall owner) and/or an affiliate of a collection of merchant brands subscribing to, or operating, a multistage value system.
  • a multistage value system may according to at least some example embodiments be provided by a third party from a remote server.
  • a value offered to a user during one or more stages of a multistage value account may be the result of, for example, an online game or games (e.g., game scores).
  • a value offered during one or more stages may be random, for example, the result of a virtual scrath- off.
  • the system may be a merchant, cross-merchant, product and/or issuer centric system.
  • a merchant multistage value system may offer a user a value at each of multiple stages, the value usable or in exchange for, among other things, making purchases from the merchant, making purchases from different stores of the merchant and/or purchasing different preferred products from the merchant.
  • a cross-merchant multistage value system which may be provided by, for example, an issuer, and may offer a user a sequence of values corresponding to a sequence of purchases from different merchants.
  • a user may be provided values usable or in exchange for making a purchase at a first merchant at a first stage, at a second merchant at a second stage, a third merchant at a third stage or any combinations of merchants with or without repeats.
  • Stages may be related to, for example, non-competitive merchants, merchants familiar to one another, merchants selected according to machine learning and/or combinations thereof.
  • a multistage value account may include stages related to companies adverse to each other with the stage placement based on preferences of a multistage value system subscriber.
  • a user may be offered value for making a sequence of purchases of a particular product or a product from a family of products (e.g., for purchases of different flavors of a particular brand of ice cream).
  • a user may be offered a single value for making a purchase at a sequence of vendors, either additional to values provided at one or more individual stages of the sequence or otherwise.
  • a multistage value system may be used to induce user behavior. For example, a user may be offered value for travelling to specific geographic areas (e.g., malls, shopping districts, community revitalization projects) or different geographic locations (e.g., game vendor, amusement park locations, recreational facilities).
  • the multistage value system may be, for example, provided via a server of a merchant, acquirer, issuer, processor, payment network, third party service provider, remote facility, device provider, and/or any other entity.
  • a multistage value account identifier may be obtained in any manner value offers may be made.
  • a multistage value account identifier may be printed as a barcode on a receipt.
  • a user may obtain a generic identifier, submit the generic identifier and receive a multistage value account identifier.
  • a user may take a picture of a generic identifier in a newspaper or a screenshot of a web based advertisement, text or email the picture to a number provided in the newspaper or advertisement and receive a multistage account identifier in return from that number.
  • Persons having ordinary skill in the art in possession of this specification will understand that many different ways of providing an identifier are achievable and contemplated
  • a multistage value account may offer value based on a number of stages completed within a period of time (e.g., one month) and/or may change value based on the length of time between stage completion and/or may change the value based on the average length of time between completion of multiple stages and/or provide value based on a period of time in which all stages are completed.
  • a multistage value account identifier may be the same for all stages, different for groupings of stages or different for each stage.
  • FIG. 43 is an illustration of a process flow chart constructed in accordance with the principles of the present invention.
  • a server may receive a multistage value account identifier (e.g., a coupon identifier of a multistage coupon) and at least a portion of purchase transaction information (Step 1305).
  • the server may use the multistage value account identifier to access multistage account data associated with the identifier, obtain a current stage associated with the multistage value account and a stage threshold, and determine that the current stage is equal to or greater than the stage threshold (Step 1310).
  • the server may verify that the purchase qualifies a user of the multistage value account identifier to receive a value associated with the current stage based on the purchase transaction information (Step 1315).
  • the server may communicate a message indicating the earned value and eligibility for a loyalty card associated with the multistage value account based on the threshold (Step 1320). User information may be received by the server in response to the message (Step 1325).
  • a multi- stage account may be associated a number of stages that may be completed in any order.
  • one stage may provide a free coffee upon purchasing a dinner from Dew-Rain-Dew Restaurant, or in real-time, for example, upon ordering, such that the coffee is enjoyed as part of the experience.
  • a second stage of the multistage value may provide, for example, a free biscuit with breakfast, and a third stage may provide, for example, a free side with an entree at lunch.
  • the user may receive an all-stage completion reward, for example, a $10 gift card.
  • an employee of Dew-Rain-Dew Restaurant may accept a multistage value account identifier at any portion of the dinner meal.
  • the employee may scan a QR Code displayed on a phone of the customer.
  • the QR code may include the multistage value account identifier and may be uploaded to a remote server along with a merchant code indicating a purchase of a qualifying dinner.
  • the customer may be provided with an SMS number (e.g., a dynamic number that changes based on time) linked to such a remote server and associated with Dew-Rain-Dew restaurant, such that the multistage value account identifier may be texted to the remote server and the purchase of the dinner confirmed simultaneously.
  • the customer may not possess, and may be provided with, a multistage value account identifier for a new, unused account, for immediate or future use.
  • a merchant may permit back credit for previously purchased products (e.g., previous meals purchased from Dew-Rain-Dew Restaurant) and may provide a URL linked to a web GUI for managing a multistage value account.
  • the remote server may keep track of the stages and their completion regardless of the temporal order of completion. For example, the remote server may receive the multistage value account identifier and a merchant flag indicative of a stage, and update the multistage value account to reflect stage completion.
  • the remote server may communicate with merchant systems to affect application of the value, and if all-stage completion is achieved, provide value and/or notice to the multistage value account user.
  • the remote server may communicate with Dew-Rain-Dew Restaurant's register or billing server such that the free coffee is properly accounted for in the bill and if all-stage completion is achieved, provide notice to the multistage value account user (directly or through Dew-rain-Dew's employee).
  • FIG. 14 is an illustration of a process flow chart constructed in accordance with the principles of the present invention.
  • a user may scan a QR Code using a phone application (Step 1405).
  • a server may receive a multistage value account identifier from the phone application and access the multistage account data associated with the identifier (Step 1410).
  • the server may determine that the account is flagged for stage completion in any order and obtain stage completion data associated with the multistage value account (Step 1415).
  • the server may communicate the flag and data to the phone application (1420).
  • the phone application may display a list of stages showing which stages are complete, which stages are yet to be completed or a combination thereof, and may display stage requirements and values for uncompleted stages, and display a value associated with completion of all stages (1425). Accordingly, the user of the multistage value account may at any time check which stages are yet to be completed and verify the all stage completion reward, adding to the festive nature of the multistage value account.
  • software and/or hardware may be included in, for example, a point-of-sale (POS) terminal that identifies a barcode.
  • POS point-of-sale
  • a POS terminal may identify a QR code as being a QR code for a specific action, such as to authorize payment for a transaction.
  • the barcode such as a QR code, may identify routing information for that barcode.
  • the barcode as well as additional data such as basket level purchase data and other data associated with a transaction (e.g., tax amount) may be communicated to the routing identity in the barcode.
  • the barcode may identify routing information and include the additional data.
  • the barcode and/or associated data may be routed to the routing identity for further processing.
  • multiple barcodes may have been utilized with a purchase. For example, one or more coupon barcodes may have been used for discounts, a loyalty barcode may have been utilized for loyalty account identification, an installment barcode may identify a user's desire to pay for a purchase in installments, a points barcode may indicate that a purchase is to be paid with points (e.g., loyalty points) and a payment barcode may have been provided to complete payment for the transaction.
  • a barcode such as a QR code
  • a QR code may be encoded in a manner to convey a greater amount of data than a conventional QR code, using for example a high capacity QR format (e.g., 177 x 177), multi-level data, data compression, or defined combination function flags.
  • Mmultiple QR codes may be condensed into a single QR code.
  • a user may provide a POS terminal with a QR code that includes payment routing, loyalty, discount, installment, and/or points information, and/or other information.
  • a QR code may, for example, indicate combinations of QR codes to be communicated to a routing identity (e.g., a payment QR code with an installment QR code for a third party installment plan provider to define an installment plan).
  • each barcode may initiate a different process and information may be routed to those different processes (either in parallel or in serial).
  • the identification of the type of process e.g., coupon, loyalty, payment, installment, points
  • the system at the routing identity may receive, for example, all information, including all barcodes, and may determine the type of each barcode and initiate processes based off that determination.
  • the type of the barcode may be identified as a payment type.
  • the barcode may then include additional identifying information, such as the payment network for the payment account, the bank for the payment account, the user's account from that bank account, and additional discretionary data.
  • additional discretionary data may be a dynamic security code that changes with every use.
  • different barcodes may be provided by a device (e.g., a phone, watch, or battery powered card with a display) to make a payment at a store (e.g., via a point-of-sale system) and each of those barcodes may be associated to the same payment account from the same payment network and issuing bank with the difference being, at least in part, dynamic security data.
  • a device e.g., a phone, watch, or battery powered card with a display
  • a store e.g., via a point-of-sale system
  • each of those barcodes may be associated to the same payment account from the same payment network and issuing bank with the difference
  • magnetic stripe information could be, for example, represented as a barcode.
  • a dynamic magnetic stripe security code may be provided as part of the dynamic magnetic stripe data. Such data may be communicated to a point-of-sale terminal, identified and routed to that identified process, and the identified process may replace the barcode with magnetic stripe data, or generate magnetic stripe data, and may communicate this information to a payment network and perform an authorization process for that magnetic stripe data with a payment network.
  • a token may be utilized, such as a token issued by a token issuing entity, as the data for payment authorization.
  • a message may be sent back to the point-of-sale terminal that causes the transaction to be completed.
  • This can be done in many ways. For example, an amount of value may be stored in escrow and the point-of-sale terminal may be provided with indication that stored value is being utilized for the purchase amount and, after the transaction completes, the merchant's account may be deposited with the amount of the purchase. As such, the merchant may get access to funds quickly after a purchase transaction occurs.
  • merchants may enter into contracts to accept the payment network's issuers barcodes for various types of payment (e.g., debit, credit, pre-paid) and transactions may be authorized and merchants paid within these terms.
  • types of payment e.g., debit, credit, pre-paid
  • Bank issuers may include their own wallets that run their own cards as dynamic barcodes, such as dynamic QR codes.
  • Phone manufactures may find such features difficult to block as such features do not include the use of secure hardware on the devices.
  • the barcodes may be generated locally using local algorithms (e.g., stored in white box crypto approaches on the phone applications) or may be retried from a third party (e.g., retrieved and stored from a secure cloud). Such barcodes may be retrieved in batches (e.g., of 5 or more, 10 or more, 100 or more, etc). Such barcodes may be deleted after use so that the information is not retained on the device in any form.
  • a multi-issuer and multi-network wallet may be provided that permits a consumer to load in dynamic barcodes from various issuers.
  • a user may be able to enter in his/her payment information either manually or via a phone (with an OCR component of an application reading information from the picture of the card).
  • a token service may then be called to obtain an eligible payment token for the card. This token may be converted into a static or dynamic QR code.
  • a Dynamic Payment Barcode e.g., as a Dynamic Payment Barcode
  • the dynamic payment process may check to determine if other barcodes are utilized (e.g., a coupon barcode, loyalty barcode, etc.) and all barcode may be processed in order to properly complete a transaction.
  • the barcode may identify the network and the appropriate information for that network may be communicated to obtain authorization of the payment information.
  • a decline may be received from the network and cause a decline communication to be sent to the point-of sale.
  • An approval may be received from the network and cause an approval communication to be sent to the point of sale.
  • Additional information may be sent to the network, such as additional information to assist with other processes such as fraud detection and marketing insight evaluation.
  • the identification steps may be included in the point- of-sale.
  • a point-of-sale may simply be the phone itself.
  • a consumer may send a barcode from his/her phone to another phone and that phone itself may authorize the barcode and act as a barcode point-of-sale and/or identification and payment authorization process.
  • a payment card or other device such as a payment phone or watch, can interact with a point-of-sale terminal to complete a transaction.
  • Multiple stages of communications from the payment device to the payment terminal and from the payment terminal to the payment device can be provided so that each device or process can identify itself to each other, securely confirm the other identity is authorized to conduct a transaction, and provided information for the authorization of a payment transaction.
  • the point-of-sale terminal may route such communications to/from a merchant processor which may route parts of the communication to/from a payment network process, which may route part of the communications to/from an issuing processor that issued the payment device to the end consumer.
  • the transaction may be communication between the payment device and point-of-sale terminal, for example, a contact chip connection, a contact or wireless magnetic stripe connection, a contactless connection, or through a visible connection such as a single-stage or multipl-stage barcode or QR code.
  • a multiple-stage barcode may be a barcode that changes the information displayed throughout a payment transaction process so that multiple different types of information are displayed at different times over the same display area.
  • This information may include, the amount authorized, additional monetary amounts, the country code of the terminal, the terminal verification results, the transaction currency code, the transaction data, the transaction type, the data authentication code, the iCC dynamic number, the CVM results, the transaction time, merchant custom data, transaction date, tvr, unpredictable number, whether the transaction was authorized or declined, or any type of data retrievable by the payment card.
  • a payment card may be battery-powered or non- battery powered and may include buttons to permit a consumer to select different payment accounts (e.g., debit, credit, pre-paid), payment options (e.g., pay with points, pay with equal monthly payments such as 3, 6, 9, 12, 15, 18, 21, 24, 27, 30, 36, 39, 42, 45, or 48 monthly payments, or other payment features (e.g., a password- entry system where a correct password is needed to use the card to complete a purchase).
  • payment accounts e.g., debit, credit, pre-paid
  • payment options e.g., pay with points, pay with equal monthly payments such as 3, 6, 9, 12, 15, 18, 21, 24, 27, 30, 36, 39, 42, 45, or 48 monthly payments
  • other payment features e.g., a password- entry system where a correct password is needed to use the card to complete a purchase.
  • the payment devices may include multiple processors - such as a general processor for managing the general operation of the device and a payments processor or secure memory element for managing all or part of the payment data and payment process of the device.
  • processors such as a general processor for managing the general operation of the device and a payments processor or secure memory element for managing all or part of the payment data and payment process of the device.
  • Data not associated with the direct authorization of a payment may be copied from information requested from the payment device and stored and utilized for non-payment or payment features.
  • a card may have a display such as a pixelated display operable of displaying a cardholders payment network logo, cardholder name, payment account number, payment expiration date, payment security code for online transactions (e.g., CVV2, CVC2), card name, and other pieces of information.
  • a display such as a pixelated display operable of displaying a cardholders payment network logo, cardholder name, payment account number, payment expiration date, payment security code for online transactions (e.g., CVV2, CVC2), card name, and other pieces of information.
  • Messages associated with a particular time and/or date may be pre-stored. For example, messages associated with an anniversary date of the issuance of the card, consumer birthday information, country holidays, religious events, or any notification or message associated with a particular time or date. For example, a message wishing the consumer a happy birthday and providing the consumer with a QR code coupon for a certain amount in value may be displayed based on a date received during a payment transaction (and, for example, a clock in the payment device that updates the stored date as time passes).
  • a birthday event may trigger a feature such as a game feature where a consumer gets to pick a gift box from a number of gift boxes where each or one ore of the gift boxes has a different amount or type of value stored in it.
  • a marketing campaign may be provided where on your birthday you have the chance to win a statement credit for your payment card bill in different amounts based on, for example, an instant no- purchase necessary sweepstakes where on the cardholders birthday the cardholder is provided instant statement credit value based on different odds of receiving different amounts of value.
  • Pre-stored messages based on time could be provided so that a different message is released at a particular time (e.g., 9am EST) every day. Date-based messages could include for example, new years, Christmas, Ramadan, each day of hannakah, memorial day, independence day, election day, etc.
  • Payment devices such as payment cards, may include, for example, one or more displays, light emitting diodes, programmable magnetic stripes that can change the magnetic stripe data on the magnetic stripe, programmable EMV chips, programamble contactless chips, cellular chips and antennas for downloading data from a remote source, manual interfaces, sound interfaces, etc
  • Security features may be provided based on the received data.
  • a dynamic security code may be changed based on time and/or date information received from the payment device during an authorization transaction on a two-way authorization process (e.g., via an EMV or contactless transaction).
  • the dynamic security code may provide a dynamic in-stripe security code (e.g., CVC1/CV1) and on-line security code (e.g., CVC2/CVV2). They may be the same or different security codes based on time and/or date or other information received and multiple types of information received (e.g., a different code may be provided based on time and country information received during a payment transaction).
  • Pre-stored messages may be provided based on any information received such as, for example, country code.
  • a welcome message may be provided after a consumer makes a payment transaction in a new country that welcomes the user to the country and provides the consumer with payment information (e.g., exchange rates) based on that country.
  • payment information e.g., exchange rates
  • a card may display information on the transaction (e.g., amount of the transaction) in both the local and foreign currency by using information received and/or logic on the card.
  • Transaction applets may be provided that changes the account or payment option information based on what was received during the transaction. For example, if a US card account is utilized in Spain then the card may change the account to a Spanish account for future transactions (unless otherwise directed by the cardholder). In doing so, the payment device can receive information and change the way the payment devices operated based on the received information.
  • Any information could enable a new account (e.g., debit credit) or payment option (e.g., EMI, pay with points) for the current or a future transaction.
  • a card can terminate a transaction based on information received and start a subsequent transaction (e.g., by having the cardholder remove and replace the card in a chip contact reader or reinstitute a new contactless transaction, etc.
  • Payment terminals can be constructed to reinstitute transactions automatically if a transaction fails.
  • Example types of information receivable to cause modification of an applet, or by an applet may include, for example:
  • encrypted personalization data may be sent over a transmission link (e.g., cell network, Bluetooth, NFC, etc.).
  • a perso data block may have a unique session identifier preprogrammed into a secure element (SE) which may be used as part of an decryption process.
  • SE secure element
  • Data may be encrypted at multiple levels.
  • a two level embodiment may include transmission link encryption.
  • An entire block of perso data may be encrypted (e.g., 3DES, AES, etc.) during transmission.
  • This block may be decrypted by, for example, a general purpose processor (GP).
  • the GP may use a unique Session Identifier to request the transmission decryption key from the Secure Element.
  • Such a two level embodiment may further include encryption of sensitive perso data (personal data of a cardholder) - sensitive perso data such as UDKs may be encrypted such that they will never be in the clear.
  • This information may be sent encrypted to the SE (such as a secure element chip) and may be decrypted inside the Secure Element. This decryption process may be performed by an applet installed on the SE.
  • Cards may be preloaded with sets of keys in the SE that are associated with: Transmission Link Key - This key may be utilized by the GP to decrypt the entire perso data block that was received.
  • the GP may provide the unique session identifier provided with the perso data Block to the SE such that the appropriate key can be provided.
  • Multiple unique transmission keys (each associated with a unique Session Identifier) may be preloaded such that multiple perso upgrades can be performed over the life of the card. This process may be protected from attacks by, for example, only allowing three attempts to request the transmission link key and if the proper unique session identifier is not provided within three attempts, the process may be blocked going forward.
  • Sensitive Perso Data Key - This key may be utilized by the SE to decrypt sensitive perso data.
  • the unique session identifier may be provided to the SE to be able identify the proper preloaded keys to decrypt the sensitive perso data.
  • Multiple unique sensitive perso data keys (each associated with a unique Session Identifier) may be preloaded such that multiple perso upgrades may be performed over the life of a card. This process may be protected from attacks by only allowing three attempts to provide a unique session identifier and if the proper unique session identifier is not provided within three attempts, the process will be blocked going forward.
  • Preloaded Perso Data Acording to some example embodiments, preloading either multiple entire sets of perso data or multiple partial sets of perso data (which may be unique to this card) which may be triggered to be used by sending a signal to the card over a transmission link (e.g., cell network, Bluetooth, NFC, etc.) to change account information.
  • a transmission link e.g., cell network, Bluetooth, NFC, etc.
  • Partial Sets of Perso Data In order to minimize the amount of data preloaded, only the unique data associated with an account upgrade (PAN, UDKs, certificates, etc.) may be preloaded. Multiple partial sets of Perso Data which may, for example, include changes based on an update to PAN sequence number only or entirely different PANs may be preloaded on the SE. Each of the Partial Sets of Perso Data may be associated with a unique account identifier programmed into the SE. When a change in account is deemed necessary a signal may be sent to the card including the unique account identifier associated with the next set of account data. This unique account identifier may be sent to the SE and if it matches the next account data the card may begin using that Account information. This process may be protected from attacks by only allowing three attempts to provide a unique account identifier and if the proper unique account identifier is not provided within three attempts, the process may be blocked going forward.
  • a slider may be used to select different features instead of, for example, a button.
  • FIG. 46 is a diagram illustrating example loyalty processing hardware configurations according to some example embodiments.
  • a region may be any geographical, commercial and/or political division, such as a country, state, province, territory, consumer market, and/or the like.
  • [0801] discloses a non-limiting example according to example embodiments of loyalty processing.
  • the particular elements and combinations of elements of [ProcessingAPI] provide an example only and is not to be construed in a mandatory nature generally.
  • the mandatory nature applies to the specific example provided in accordance with some example embodiments and may be permissive according to other example embodiments.
  • the example provided by [ProcessingAPI] is shown with respect to one or more languages (e.g., XML), the disclosure is not limited to such language or languages. Persons of ordinary skill, once having read [ProcessingAPI], will at once envisage the multitude of different implementations of loyalty processing according to example embodiments.
  • [StackedOfferAPI] discloses a non-limiting example according to example embodiments of stacked offers processing.
  • the particular elements and combinations of elements of [StackedOfferAPI] provide an example only and is not to be construed in a mandatory nature generally.
  • the mandatory nature applies to the specific example provided and is in accordance with some example embodiments and may be permissive according to other example embodiments.
  • the example provided by [StackedOfferAPI] is shown with respect to data transmission of objects using a particular file format (e.g., JSON), the disclosure is not limited to such format.
  • Persons of ordinary skill, once having read [StackedOfferAPI] will at once envisage the multitude of different ways that stacked offers may be processed (e.g., stacked offer issuance).
  • [DynamicsLoyaltyComponents] discloses a non- limiting example according to example embodiments of barcode formatting that may represent a variety of different types of offers in loyalty processing with backwards and forwards compatibility, providing at least the benefits of fast and direct access to offer details and payload validation before issued offer details are queried.
  • the particular elements and combinations of elements of [DynamicsLoyaltyComponents] provide an example only and is not to be construed in a mandatory nature generally. For example, while terms of a mandatory nature appear, the mandatory nature applies to the specific example provided and is in accordance with some example embodiments and may be permissive according to other example embodiments.
  • [0804] discloses a non-limiting example according to example embodiments of loyalty processing combinational logic.
  • elements usable alone or in combination with other elements provide a robust, reliable, scalable loyalty processing apparatus/system/platform operable to process a high volume of transactions, for example ten thousand transactions per second and more than one billion transactions annually, with sub-second response time, and operable to process a range of offer types and data, and provide information and features.
  • the use of the term user may represent a loyalty system provider customer (e.g., restaurant chain), a customer may be a user or consumer that is a current or potential customer.
  • a loyalty processing apparatus/system/platform upon parsing of a barcode, may be operable to, using the individual components, verify that a coupon definition is valid (e.g., based on the coupons setup in the apparatus or system) and to ensure the individual coupon is still able to be utilized.
  • Offer Processing see for example [StackedOfferAPI] .
  • Discount Processing After parsing a basket and reviewing the coupon definition, the apparatus or system may be operable to run discount processing rules triggered by conditions being met for a transaction. Offer attributes may be, for example, time based, location based, basket amount, SKU based and/or channel based.
  • an apparatus/system/platform may track purchases made by unique card IDs/customers and award visits, points and/or special offers as customers reach their individual thresholds.
  • the tracking may be performed by, for example, storing visit/points for individual QR Codes.
  • User Level Rewards According to some example embodiments, all (or some) individual loyalty users may be tracked independently. Unique rewards may be awarded at the customer level such that a loyalty apparatus/system/platform is operable to provide individualized customer-specific offers and rewards to be configured.
  • Basket Verification Logic upon receipt of a POS XML including transaction basket SKUs, an apparatus/system/platform may compare the SKUs to rules to verify that that the transaction is a qualifying transaction.
  • an apparatus/system/platform may be operable to provide users the ability to stack multiple offers on a customer's account.
  • the offer can be added in real time by calling the API and/or using a stacked offer upload feature in a dashboard.
  • Product-specific discounts may be tiered on top of standard points/visit- based loyalty transactions.
  • an apparatus/system/platform may provide functionality to rotate through predefined individual product rewards or to define odds to give unique discounts/offers based on either purchase history or customer profile.
  • a suite of API endpoints may be provided to facilitate customer tracking of the customer's loyalty accounts.
  • one or more endpoints may provide customer loyalty account balance tracking.
  • API disclosure See, for example, API disclosure.
  • a suite of API endpoints may be provided to facilitate customer tracking of the customer's loyalty accounts.
  • one or more endpoints may be provided to facilitate user registration of consumers (e.g., potential customers or customers) into a loyalty program.
  • an apparatus/system/platform may provide an option of customer registration to a barcode (QR code) or not.
  • the apparatus/system/platform may track the loyalty visits/points/etc...by QR code (at the QR level) and users and/or customers may begin tracking loyalty before the customer is known.
  • Real-Time Issuance See, for example, API disclosure.
  • a suite of API endpoints may be provided to facilitate user or customer tracking of the customer's loyalty accounts.
  • one or more of these endpoints may be provided to facilitate issuance of consumer QR codes in real time.
  • an apparatus/system/platform may provide customer/consumer challenges that upon completion automatically rewards the customer/consumer with discounts and rewards based on the results.
  • an apparatus/system/platform may provide users the ability to segment customers into individual consumer segments. Each segment may be associated to the award of a unique offer type (e.g., unique among segments). Users may move customers/consumers in and out of unique offers.
  • a unique offer type e.g., unique among segments.
  • an apparatus/system/platform may determine any SKU to have any number of discounts applied. For example, Percentage Dollar Amount.
  • Hosting Strategy See, for example, FIG. 46.
  • an apparatus/system/platform may provide a cloud-based approach seggregating user traffic by region.
  • an apparatus/system/platform may provide container-based auto-scaling APIs with 0 transaction handling latency by providing demand based allocation (addition or removal) of, for example, hardware and virtual machines ("VMs") as required in real time.
  • VMs hardware and virtual machines
  • maximum and minimum thresholds on the number of concurrent transactions may be set by the user and/or provider to trigger demand based auto-scaling.
  • wallet cards may be preloaded with multiple cards, for example multiple issuer cards or multiple network cards.
  • the wallet card may be updated wirelessly to add, remove, or modify, cards that are stored on the wallet card.
  • FIG. 49 shows cards and architectures according to example embodiments.
  • card 100 may include, for example, dynamic magnetic stripe communications device 101, one or more displays (e.g., displays 112, 113 and 125), permanent information 120, one or more buttons (e.g., buttons 130-134 and 197-199) and/or dynamic number 114.
  • Dynamic number 114 may include permanent portion 111. Permanent portion 111 may be, for example, printed, embossed and/or laser etched on card 100.
  • Card 100 may conform to one or more ISO standards, for example ISO/IEC 7810 and ISO/IEC 7813. In some embodiments, the card may follow set physical dimension guidelines, for example the card may be 33 one thousands of an inch thick, plus or minus 2 one thousands of an inch.
  • Display 112 may utilized to entirely, and/or partially, display a dynamic number.
  • Display 113 may be utilized to display a dynamic code (e.g., a dynamic security code).
  • Display 125 may display card information, logos, barcodes, holograms, and/or multiple lines of information.
  • a display e.g., at least one of displays 112, 113 and 125
  • a bi-stable display may be a display that maintains an image without power.
  • Permanent information 120 may include, for example, information specific to a user (e.g., a user's name and/or username) and/or information specific to a card (e.g., a card issue date and/or a card expiration date).
  • Buttons 131-134 and 197-199 may be mechanical buttons, capacitive buttons, or a combination of mechanical and capacitive buttons. Buttons 131-134 may be used, for example, to enter information (e.g., an access code) and/or to make a selection. For example, using buttons 131-134, a user may select options displayed on display 125 that instruct card 100 to communicate (e.g., via a dynamic magnetic stripe communications device, RFID and/or exposed IC chip) a user's instructions to use one of a debit account, a credit account, a pre-paid account, or a point account for a transaction (e.g., a payment transaction).
  • a dynamic magnetic stripe communications device e.g., RFID and/or exposed IC chip
  • more than one account may be selected, for example, where a transaction may be divided between accounts.
  • card 100 may be utilized to indicate a user's desire to use a point account until the point account is exhausted and then a credit account.
  • Buttons 197 and 198 may be used, for example, to display a different card's information on more or more of the displays 112, 113, and 125.
  • a button e.g., button 199
  • Button 199 may be utilized to communicate information indicative of a user selection.
  • a user may associate applications to buttons and/or features to applications, for example, on a graphical user interface (GUI).
  • GUI graphical user interface
  • the graphical user interface may be, for example, an application manager provided by one or more entities.
  • the associations may be changed, for example, at any time, periodically, and/or upon the occurrence of an event.
  • a user may associate applications to buttons and/or features to applications by telephone, by electronic mail and/or any other communication method.
  • buttons and service provider applications may be maintained by an ecosystem provider, for example, within an ecosystem of applications, transactional methods and types of transactions.
  • a transactional method e.g., card 100
  • the ecosystem provider may receive transactional data and information indicative of a button selected by the user.
  • the ecosystem provider may determine the identity of an application associated to the button, and may communicate some or all of the information and/or transactional data to the application and/or the service provider.
  • the service provider and/or the application may provide a feature associated with the application based on the information and/or transactional data.
  • Architecture 150 may be utilized with any card (e.g., any card 100).
  • Architecture 150 may include, for example, processor 120, display 140, driving circuitry 141, memory 142, battery 143, radio frequency identification (RFID) 151, integrated circuit (IC) chip 152, electromagnetic field generators 170, 180, and 185, and read-head detectors 171 and 172.
  • Processor 120 may be any type of processing device, for example, a central processing unit (CPU) and/or a digital signal processor (DSP).
  • DSP digital signal processor
  • Processor 120 may be, for example, an application specific integrated circuit (ASIC).
  • ASIC application specific integrated circuit
  • Processor 120 may include on-board memory for storing information (e.g., drive code). Any number of components may communicate to processor 120 and/or receive communications from processor 120.
  • one or more displays e.g., display 140
  • a display driver circuit may be coupled between display 140 and processor 120.
  • Memory 142 may be coupled to processor 120.
  • Memory 142 may store data, for example, data that is unique to a particular card.
  • Memory 142 may store any type of data.
  • memory 142 may store discretionary data codes associated with buttons of card 100.
  • Discretionary data codes may be recognized by remote servers to effect particular actions.
  • a discretionary data code may be stored in memory 142 and may be used to cause a third party service feature to be performed by a remote server (e.g., a remote server coupled to a third party service such as an online voucher and/or coupon provider).
  • a remote server e.g., a remote server coupled to a third party service such as an online voucher and/or coupon provider.
  • Different third party features may be, for example, associated with different buttons and a particular feature may be selected by pressing an associated button.
  • a user may select a third party feature from a list displayed to the user. For example, the user may scroll through a list of features on a display (e.g., a display on the front of the card). A user may scroll through a list using buttons on card 100.
  • the list of features may be displayed to the user individually (e.g., one or more buttons may be used to change which feature is displayed), in groups and/or all features may be simultaneously displayed.
  • a user may select a type of payment on card 100 via manual input interfaces.
  • the manual input interfaces may correspond to displayed options (e.g., displayed on display 125) and/or may be independent buttons.
  • Selected information may be communicated to a magnetic stripe reader via a dynamic magnetic stripe communications device.
  • Selected information may also be communicated to a device (e.g., a mobile telephonic device) including a capacitive sensor and/or other type of touch sensitive sensor.
  • Architecture 150 may include any number of reader communication devices.
  • architecture 150 may include at least one of IC chip 150, RFID 151 and a magnetic stripe communications device.
  • IC chip 150 may be used to communicate information to an IC chip reader (not illustrated).
  • IC chip 150 may be, for example, an EMV chip.
  • RFID 150 may be used to communicate information to an RFID reader.
  • RFID 150 may be, for example, a RFID tag.
  • a magnetic stripe communications device may be included to communicate information to a magnetic stripe reader.
  • a magnetic stripe communications device may provide electromagnetic signals to a magnetic stripe reader.
  • architecture 150 may include electromagnetic field generators 170, 180, and 185 to communicate separate tracks of information to a magnetic stripe reader.
  • Electromagnetic field generators 170, 180, and 185 may include a coil (e.g., each may include a coil) wrapped around one or more materials (e.g., a soft-magnetic material and a non-magnetic material).
  • Each electromagnetic field generator may communicate information, for example, serially and/or in parallel to a receiver of a magnetic stripe reader for particular magnetic stripe track.
  • Architecture 150 may include read head detectors 171 and 172.
  • Read-head detectors 171 and 172 may be configured to sense the presence of a magnetic stripe reader (e.g., a read-head housing of a magnetic stripe reader). Information sensed by the read-head detectors 171 and 172 may be communicated to processor 120 to cause processor 120 to communicate information serially from electromagnetic generators 170, 180, and 185 to magnetic stripe track receivers in a read-head housing of a magnetic stripe reader.
  • a magnetic stripe communications device may change the information communicated to a magnetic stripe reader at any time.
  • Processor 120 may, for example, communicate user-specific and card-specific information through RFID 151, IC chip 150, and/or electromagnetic generators 170, 180, and 185 to card readers coupled to remote information processing servers (e.g., purchase authorization servers).
  • Driving circuitry 141 may be utilized by processor 120, for example, to control electromagnetic generators 170, 180, and 185.
  • Architecture 150 may include, for example, a light sensor (not illustrated). Architecture 150 may receive information from a light sensor. Processor 120 may determine information received by a light sensor.
  • a single wallet card operable to be loaded with information for one or more other cards, for example credit cards, debit cards, rewards cards, loyalty cards.
  • An entity for example an issuer, such as a bank, other financial institution, a network (like MasterCard® or Visa®), or a 3 rd party, would provide the wallet card.
  • the wallet card can be provided with cards already loaded.
  • an EMV chip is provided on the card that is dynamic and can communicate information specific to a selected card.
  • one or more of the displays comprise e-paper.
  • displays comprising e-paper display information using a segmented display.
  • displays comprising e-paper display information using a pixilated display.
  • buttons on the wallet card to cycle through stored cards. For example, there may be a single button that cycles sequentially through cards. In an embodiment, there may be two buttons that allow a user to cycle through cards in different orders, for example forward and backward though a sequence of cards. In other embodiments, there may be more than two buttons, for example a button for each card information stored on the wallet card. In an embodiment, logos associated with the financial institution or network associated with a specific account may also be displayed.
  • a dynamic magnetic stripe communications device on the wallet card will transmit the information related to the selected stored card. This may be communicated via a magnetic stripe emulator, magnetic stripe encoder, or wirelessly.
  • the wallet card may communicate and receive information using Bluetooth.
  • the wallet card may communicate and receive information via RFID.
  • the wallet card may communicate and receive information via the EMV chip.
  • the wallet card may communicate and receive information via LEDs and light sensors.
  • the wallet card is updated by the party that issued the wallet card, not by the user.
  • the wallet card may be issued by a banking institution, a credit institution, or any other 3 rd party.
  • the issuing party may preload one or more specific cards onto the wallet card.
  • a bank may initially load debit card information, cash- back credit card information, and airline rewards credit card information onto the wallet card.
  • the user could then use the wallet card to conduct debit transactions or credit transactions which result in different rewards (in this case cash back or airline rewards).
  • the issuing party may also modify the card information on the wallet card.
  • the user may cancel the airline rewards credit card. In this case, the issuing party would communicate instructions to the card to delete this account.
  • the issuing party may update the cash- back credit card information, for example if the card expired and the user authorized the third part to issue a replacement card. In this case, the issuing party would communicate instructions to the card to modify this account. In another example, the user may indicate that it wishes to open a new account with the issuing party, for example a low-interest credit card. In this case, the issuing party would communicate instructions to the card to add this account to the accounts stored on the wallet card.
  • deleted, modified, or added information may include EMV information.
  • an EMV chip may communicate card specific information related to the selected card.
  • a wallet card may be limited to a specific network.
  • the wallet card may be issued by a specific network, or a third party may only be authorized to provide card information for cards from a specific network on a given wallet card.
  • a credit card company such as Visa®
  • Visa® may issue a wallet card, but only permit that credit cards company's (or a select few card issuing companies) cards to be accessed using the wallet card.
  • Such a wallet card may include additional branding information identifying the wallet card, for example holograms or other logos. Some of this information may appear on the display itself.
  • a wallet card may be limited to a specific financial institution.
  • the wallet card may be issued by a specific financial institution, for example a specific bank, and may only maintain cards provided by that specific financial institution.
  • a bank such as Bank of America®, may issue a wallet card, but only permit that bank's (or a select few card issuing companies) cards to be accessed using the wallet card.
  • Such a wallet card may include additional branding information identifying the wallet card, for example holograms or other logos. Some of this information may appear on the display itself.
  • the card may go to sleep, turning off the display and all dynamic magnetic stripe communications devices. In an embodiment, within a set amount of time after the card is last interacted with, it will go to sleep. In an embodiment, the card may include a on/off button that, when pressed, will either put the card to sleep or wake it up from sleep.
  • the wallet card may also maintain and display information related to the rewards tier achieved by a user with respect to the selected card.
  • the tier may be displayed on the card, for example with the selected card information or on a separate display.
  • the issuer's logo may be modified to display the tier of the selected card. For example, if a user has achieved Visa Signature status for a specific card, the Visa logo may be modified to indicate that user has achieved Visa signature status for that card.
  • multiple tiers are possible, for example, Visa® basic, Visa Signature®, and Visa Black® or American Express Gold®, American Express Platinum®, American Express Reserve®, and American Express Black®.
  • the user may achieve different tiers, rather than specific cards.
  • the user's status may be displayed, either with the card information or on a separate display.
  • MasterCard® may issue a wallet card, where all the cards are linked and accrue points towards
  • MasterCard World Elite® status Once a user has achieved this status, for example, by making enough purchases across all stored cards, the card may indicate that the user has achieved this status.
  • FIG.50 shows an example wallet card according to example embodiments.
  • card 205 illustrates an exemplary wallet card prior to pushing a button on the wallet card.
  • Card 255 illustrates the same exemplary wallet card after pushing a button on the wallet card.
  • initially information regarding one stored card in this case the Visa 1 card, is displayed. While not shown, additional information can be displayed to the user on the same or different displays. For example, the card number may be displayed in an embodiment. In an embodiment the Visa® logo may be displayed.
  • the EMV chip Prior to pressing the button, the EMV chip will communicate information associated with the Visa 1 card that is displayed on card 205.
  • the Visa 1 card information may also be communicated via multiple means, for example a dynamic magnetic stripe emulator, a dynamic magnetic stripe encoder, or wirelessly.
  • the Visa 1 card information may also be communicated wirelessly via Bluetooth, RFID, WiFi, light (using LEDs and light sensors), as well as other wireless communication means known to those skilled in the art.
  • the EMV chip After pressing the button, the EMV chip will communicate information associated with the Visa 2 card that is displayed on card 255.
  • the Visa 2 card information may also be communicated via multiple means, for example a dynamic magnetic stripe emulator, a dynamic magnetic stripe encoder, or wirelessly.
  • the Visa 2 card information may also be communicated wirelessly via Bluetooth, RFID, WiFi, light (using LEDs and light sensors), as well as other wireless communication means known to those skilled in the art.
  • card 205 maybe able to be recharged wirelessly, for example via a user's mobile phone.
  • card 255 may determine that additional charge is needed.
  • card 255 can display a message to the user to either slow down the swipe or leave the card in the reader to allow the card to recharge.
  • the card can be powered solely by the reader, solely by the battery (allowing card 255 to simultaneously charge the battery), or a combination thereof.
  • the display is bi-stable, allowing message to remain on the display even after the card powers down.
  • the issuer or 3 rd party provided may provide messaged to the card. For example, a party may display a birthday message on the user's birthday or offer $5 of the first purchase on a user's birthday.
  • the card may display message in response to transaction events. For example, if a transaction is denied, the card may display a reason for the transaction denial (low funds or high balance) and suggest an action (user a different account or request a credit increase). By providing the user with information about transaction denials and options forward, the card may maintain its top of wallet status.
  • issuers may provide new card data (for example if a user is issued a new card) and remove old data (for example if a user's card data is expired or compromised).
  • a bi-stable display is used to provide a message to the user while conserving power.
  • FIG. 51 shows an example wallet card according to example embodiments.
  • card 305 illustrates an exemplary wallet card prior to pushing a button on the wallet card.
  • Card 355 illustrates the same exemplary wallet card after pushing a button on the wallet card.
  • the screen shows data for the entire card, for example, the card name, the card number, expiration data, a verification code (such as a CVV or CVC code), and a network logo (for example a VISA® logo). Some or all of this information may change for each card. For example, in one instance, the card number and expiration date may change, by the network logo may remain the same, for example where the two cards are of the same interchange tiers.
  • the logo may change as well, for example if the two cards belong to different interchange tiers.
  • initially information regarding one stored card in this case the Visa 1 card, is displayed. While not shown, additional information can be displayed to the user on the same or different displays.
  • the card number may be displayed in an embodiment.
  • the Visa® logo may be displayed.
  • wallet card 305 can be downloaded to the wallet card wirelessly, for example, using Bluetooth, RFID, WiFi, light, or other wireless communication means.
  • card 305 may also be updated wirelessly, for example, via a phone using Bluetooth.
  • wallet card 305 is issued by a single entity, for example a bank. That entity may provide additional cards or services through the card. For example, the entity may provide updates to a user's device, for example a mobile phone, which can wirelessly communicate information to the wallet card. In this way, additional card or services may be provided to the user, as discussed in more detail below.
  • wallet card 305 may be limited to cards associated with a specific issuer, cards associated with a specific network, or cards associated with a specific network and specific issuer.
  • FIG. 52 shows exemplary wallet card displays according to example embodiments.
  • card display 405 illustrates an exemplary wallet card display communicating that the monthly payment is due.
  • other account status updates may be provided, for example, points accumulated, points redeemed, points expiring, recent transactions, etc.
  • Card display 410 illustrates an exemplary wallet card display communicating that a user is approaching their spending limit.
  • other warnings may be provided, for example, finance charges, unusual activity notifications, etc.
  • Card display 415 illustrates an exemplary wallet card display communicating that the user has been offered a gift. This may be offered by the issuer, network, or a third party. Gifts may be offered in response to reaching certain milestones, for example accumulating a certain number of points, or randomly, as desired by the party offering the gift.
  • Card display 420 illustrates an exemplary wallet card display communicating that the user can now apply for a new card provided by the issuer and/or the network. It may also be used to indicate that a new card, that was previously applied for, has been approved and downloaded to the card. This may allow issuers and networks to provide cards to their current customers instantly, without incurring the cost associated with manufacturing and mailing a new physical card.
  • Card display 425 illustrates an exemplary wallet card display communicating a special event.
  • this may be a generic event, for example New Year Celebrations, or may be specific to the user (for example, happy birthday) or the network or issuer (for example, corporate milestone events).
  • Card display 430 illustrates an exemplary wallet card display communicating a loyalty program offered by an issuer or a partner of the issuer.
  • an issuer may provide certain rewards based on usage of the card.
  • a third party may partner with the issuer, for example a coffee shop, to provide loyalty rewards and incentives through the card.
  • Card display 435 illustrates an exemplary wallet card display communicating a coupon.
  • the coupon may be delivered as a UPC or bar code.
  • the merchant associated with a coupon may be disclosed, but the actual coupon may not be disclosed until it is redeemed.
  • Card display 440 illustrates an exemplary wallet card display communicating status upgrades for the user.
  • the card may be issued by an airline. Once a user has attained a specific flight status, information may be communicated to the user via the card.
  • Card display 445 illustrates an exemplary wallet card display may communicate points earned during transactions. In an embodiment, the display may also disclose the total points accumulated by the user.
  • Card displays 450 and 455 illustrates an exemplary wallet card display may provide information regarding associated games. In an embodiment, users may earn gaming rewards by using their card or rewards may be provided to users by the issuer, and communicated to the user via the card.
  • Card display 460 illustrates an exemplary wallet card display communicate that a user has entered, or has won, a sweepstakes.
  • FIG. 53 shows an example wallet card according to example embodiments.
  • the top card illustrates an exemplary wallet card prior to pushing a button on the wallet card.
  • the bottom card 355 illustrates the same exemplary wallet card after pushing a button on the wallet card.
  • the card holder's name is embossed on the card
  • the card holder's name is provided on a display.
  • the card holder name display can be a bi- stable display. Initially, the card can be manufactured without any information on the display. Once the card is ready to be personalized, the card holder's name can be programmed into the card. In an embodiment, at any point in the future, the card may be initialized, and the card holder's name can be displayed. In an embodiment, from that point forward, the card holder's name can always be displayed. In an embodiment, the card holder's name can be displayed each time the card is powered on, and removed each time the card is powered off.
  • FIG. 54 shows dynamic magnetic stripe 600 that may include a printed circuit board (PCB) and an adhesive layer (not shown) on top of the PCB.
  • the dynamic magnetic stripe 600 may include a dynamic magnetic stripe communications device 602, a first magnet 604, and a second magnet 606.
  • the dynamic magnetic stripe 600 may also include a shield 608.
  • Dynamic magnetic stripe communications device 202 may be configured to communicate multiple tracks of electromagnetic data, for example, two tracks of electromagnetic data, by electromagnetic generator to read-heads of a magnetic stripe reader by appropriate control of current conducted by coils within dynamic magnetic stripe communications device 602.
  • Dynamic magnetic stripe communications device 602 may be configured to be narrower than a traditional magnetic stripe. For example the entire width of dynamic magnetic stripe 600, including dynamic magnetic stripe communications device 602, first magnet 604, and second magnet 606 may be approximately equal to the width of a traditional magnetic stripe, for example about 10 mm wide. In an embodiment, dynamic magnetic stripe communications device 602 may be about 5 mm wide. In an embodiment, dynamic magnetic stripe communications device 602 is flexible.
  • First magnet 604 and second magnet 606 may be operable to bias electromagnetic data communicated by dynamic magnetic stripe communications device 602.
  • first magnet 604 and second magnet 606 may be operable to increase the amplitude of the electromagnetic data communicated by dynamic magnetic stripe communications device 602 to allow a magnetic read head to receive the electromagnetic data.
  • first magnet 604 and second magnet 606 may be operable to increase the amplitude of the electromagnetic data transmitted by different portions of dynamic magnetic stripe communications device 602 so that a magnetic read head located at a distance, for example, 1 ⁇ 4 of an inch, an inch, or two inches away, can receive the data.
  • the magnetic read head may be located at least of an inch away, at least one inch away, or at least two inches away.
  • first magnet 604 and second magnet 606 may be configured to maintain a constant magnetic field amplitude across the length of dynamic magnetic stripe communications device 602.
  • first magnet 604 can be configured to bias one track of electromagnetic data and second magnet 606 can be configured to bias a second track of electromagnetic data.
  • first magnet 604 and second magnet 606 may be configured to reduce or eliminate cross talk between different tracks of the electromagnetic data, for example between a first and a second track of electromagnetic data.
  • first magnet 604 and second magnet 606 are flexible. In an embodiment, first magnet 604 and second magnet 606 are directly adjacent to dynamic magnetic stripe communications device 602. In an embodiment, first magnet 604 and second magnet 606 are close to but separated from dynamic magnetic stripe communications device 602.
  • shield 608 may be operable to inhibit or block electromagnetic data communicated by dynamic magnetic stripe communications device 602. In an embodiment, shield 608 may be operable to inhibit or block electromagnetic effects. For example, this may increase the probability that a card is correctly read by a magnetic stripe reader with two read heads, positioned on opposite sides of the card and offset.
  • shield 608 comprises a material that is non-magnetic and conductive, for example copper.
  • shield 608 comprises a material that is magnetic and conductive.
  • shield 608 comprises a material that is a combination of magnetic and non-magnetic material.
  • shield 608 is as wide as dynamic magnetic stripe communications device 602.
  • shield 608 comprises a plurality of shield material, for example a strip of shield material associated with each track.
  • shield 608 is as wide as dynamic magnetic stripe 600.
  • shield 608 is wider than dynamic magnetic stripe 600.
  • shield 608 is flexible.
  • FIG. 55 shows a traditional magnetic stripe 730 and a dynamic magnetic stripe 705, each of which may include printed circuit board (PCB) and an adhesive layer (not shown) on top of the PCB.
  • traditional magnetic stripe 730 is similar to magnetic stripes found on traditional cards, for example static credit cards.
  • dynamic magnetic stripe 705 is similar to dynamic magnetic stripe 600 illustrated in Fig. 6 and discussed above.
  • Dynamic magnetic stripe 705 may include dynamic magnetic stripe communications device 715, first magnet 710, second magnet 720, a first sensor 735a, and a second sensor 735b, as illustrated in Fig. 55.
  • dynamic magnetic stripe 715 may also include shield 725.
  • Dynamic magnetic stripe communications device 715 may be configured to communicate multiple tracks of electromagnetic data, for example, two tracks of electromagnetic data, by electromagnetic generator to read-heads of a magnetic stripe reader by appropriate control of current conducted by coils within dynamic magnetic stripe communications device 715.
  • Dynamic magnetic stripe communications device 715 may be configured to be narrower than a traditional magnetic stripe. For example the entire width of dynamic magnetic stripe 705, including dynamic magnetic stripe communications device 715, first magnet 710, and second magnet 720 may be approximately equal to the width of a traditional magnetic stripe, for example about 10 mm wide. In an embodiment, dynamic magnetic stripe communications device 715 may be about 5 mm wide. In an embodiment, dynamic magnetic stripe communications device 715 is flexible.
  • First magnet 710 and second magnet 720 may be operable to bias electromagnetic data communicated by dynamic magnetic stripe communications device 715.
  • first magnet 710 and second magnet 720 may be operable to increase the amplitude of the electromagnetic data communicated by dynamic magnetic stripe communications device 715 to allow a magnetic read head to receive the electromagnetic data.
  • first magnet 710 and second magnet 720 may be operable to increase the amplitude of the electromagnetic data transmitted by different portions of dynamic magnetic stripe communications device 715 so that a magnetic read head located at a distance, for example, 1 ⁇ 4 of an inch, an inch, or two inches away, can receive the data.
  • the magnetic read head may be located at least of an inch away, at least one inch away, or at least two inches away.
  • first magnet 710 and second magnet 720 may be configured to maintain a constant magnetic field amplitude across the length of dynamic magnetic stripe communications device 715.
  • first magnet 710 can be configured to bias one track of electromagnetic data and second magnet 720 can be configured to bias a second track of electromagnetic data.
  • first magnet 710 and second magnet 720 may be configured to reduce or eliminate cross talk between different tracks of the electromagnetic data, for example between a first and a second track of electromagnetic data.
  • first magnet 710 and second magnet 720 are flexible. In an embodiment, first magnet 710 and second magnet 720 are directly adjacent to dynamic magnetic stripe communications device 715. In an embodiment, first magnet 710 and second magnet 720 are close to but separated from dynamic magnetic stripe communications device 715.
  • shield 725 may be operable to inhibit or block electromagnetic data communicated by dynamic magnetic stripe communications device 715. In an embodiment, shield 725 may be operable to inhibit or block electromagnetic effects. For example, this may increase the probability that a card is correctly read by a magnetic stripe reader with two read heads, positioned on opposite sides of the card and offset.
  • shield 725 comprises a material that is non-magnetic and conductive, for example copper.
  • shield 725 comprises a material that is magnetic and conductive.
  • shield 725 comprises a material that is a combination of magnetic and non-magnetic material.
  • shield 725 is as wide as dynamic magnetic stripe communications device 715.
  • shield 725 comprises a plurality of shield material, for example a strip of shield material associated with each track.
  • shield 725 is as wide as dynamic magnetic stripe 705.
  • shield 725 is wider than dynamic magnetic stripe 705.
  • shield 725 is flexible.
  • shield 725 may be operable to inhibit or block electromagnetic data communicated by dynamic magnetic stripe communication device 715 and/or traditional magnetic stripe 730. In an embodiment, shield 725 may be operable to inhibit or block any electromagnetic data. In an embodiment, shield 725 comprises a material that is non-magnetic and conductive, for example copper. In an embodiment, shield 725 comprises a material that is magnetic and conductive. In an embodiment, shield 725 comprises a material that is a combination of magnetic and non- magnetic material. In an embodiment, shield 725 is flexible.
  • first sensor 735a and second sensor 735b may be operable to detect the presence of a read-head.
  • first sensor 735a and second sensor 735b may be operable to generate a voltage in relation to magnetic fields it experiences.
  • first sensor 735a and second sensor 325b may be Hall sensors, or other sensors that are affected by the "Hall effect.”
  • first sensor 325a and second sensor 735b may be configured to increase the voltage output when a magnetic read-head passes over the card.
  • first sensor 735a and second sensor 735b can be configured to generate a different change in voltage when a magnetic read-head passes under the card.
  • first sensor 735a and second sensor 735b may be configured to decrease the voltage output when a magnetic read-head passes under the card.
  • the device is able to determine if a magnetic read-head is passing over or under the card, and only activate dynamic magnetic stripe 705 when the read head is over the correct side of the card.
  • the device may determine which direction it is being traveling, for example if it is being swiped through a payment reader. This will allow it to output data on dynamic magnetic stripe communications device 715 in the appropriate order using the appropriate formatting.
  • FIG. 56 illustrates a device containing two dynamic magnetic stripes stacked within the device 800, each operable to communicate with read heads located proximate to opposite sides of the device.
  • the first dynamic magnetic stripe comprises a dynamic magnetic stripe communications device 805, a first magnet 810, and a second magnet 815 and the second dynamic magnetic stripe comprises a dynamic magnetic stripe communications device 830, a first magnet 825, a second magnet 835, a first sensor 840a, and a second sensor 840b.
  • Dynamic magnetic stripe communications devices 805 and 830 may be configured to communicate multiple tracks of electromagnetic data, for example, two tracks of electromagnetic data, by electromagnetic generator to read-heads of a magnetic stripe reader by appropriate control of current conducted by coils within dynamic magnetic stripe communications devices 805 and 830.
  • Dynamic magnetic stripe communications devices 805 and 830 may be configured to be narrower than a traditional magnetic stripe. For example the entire width of each dynamic magnetic stripe, including dynamic magnetic stripe communications devices 805 and 830, first magnets 810 and 825, and second magnet 815 and 835 may be approximately equal to the width of a traditional magnetic stripe, for example about 10 mm wide. In an embodiment, dynamic magnetic stripe communications devices 805 and 830 may be about 5 mm wide. In an embodiment, dynamic magnetic stripe communications devices 805 and 830 is flexible.
  • first magnets 810 and 825 and second magnets 815 and 835 may be operable to bias electromagnetic data communicated by dynamic magnetic stripe communications devices 805 and 830.
  • first magnets 810 and 825 and second magnets 815 and 835 may be operable to increase the amplitude of the electromagnetic data communicated by dynamic magnetic stripe communications devices 805 and 830 to allow a magnetic read head to receive the electromagnetic data.
  • first magnets 810 and 825 and second magnets 815 and 835 may be operable to increase the amplitude of the electromagnetic data transmitted by different portions of dynamic magnetic stripe communications devices 805 and 830 so that a magnetic read head located at a distance, for example, 1 ⁇ 4 of an inch, an inch, or two inches away, can receive the data.
  • the magnetic read head may be located at least of an inch away, at least one inch away, or at least two inches away. In some embodiments, the magnetic read head may be located less than 1 ⁇ 4 of an inch away, less than one inch away, or less than two inches away. In some embodiments, the magnetic read head may be located from about 1/10 of an inch away to about 3 inches away.
  • first magnets 810 and 825 and second magnets 815 and 835 may be configured to maintain a constant magnetic field amplitude across the length of dynamic magnetic stripe communications devices 805 and 830. In an embodiment, first magnets 810 and 825 can be configured to bias one track of electromagnetic data and second magnets 815 and 835 can be configured to bias a second track of electromagnetic data.
  • first magnets 810 and 825 and second magnets 815 and 835 may be configured to reduce or eliminate cross talk between different tracks of the electromagnetic data, for example between a first and a second track of electromagnetic data.
  • first magnets 810 and 825 and second magnets 815 and 835 are flexible.
  • first magnets 810 and 825 and second magnets 815 and 835 are directly adjacent to dynamic magnetic stripe communications devices 805 and 830, respectively.
  • first magnets 810 and 825 and second magnets 815 and 835 are close to but separated from their respective dynamic magnetic stripe communications devices 805 and 830.
  • shield 820 may be operable to inhibit or block electromagnetic data communicated by dynamic magnetic stripe communications device 805. In an embodiment, shield 820 may be operable to inhibit or block electromagnetic effects. For example, this may increase the probability that a card is correctly read by a magnetic stripe reader with two read heads, positioned on opposite sides of the card and offset.
  • shield 820 comprises a material that is non-magnetic and conductive, for example copper. In an embodiment, shield 820 comprises a material that is magnetic and conductive. In an embodiment, shield 820 comprises a material that is a combination of magnetic and non-magnetic material. In an embodiment, shield 820 is as wide as dynamic magnetic stripe communications devices 805 or 830.
  • shield 820 comprises a plurality of shield material, for example a strip of shield material associated with each track.
  • shield 820 is as wide as one or both dynamic magnetic stripes. In an embodiment, shield 820 is wider than one or both dynamic magnetic stripes. In an embodiment, shield 820 is flexible.
  • first magnets 810 and 825 may be a single magnet, e.g., to make handling and manufacturing easier. For example, using a single magnet may eliminate issue of manufacturing a device with two magnets whose magnetic poles are oriented in the same direction in proximity of each other.
  • a single first magnet may be configured to maintain a constant magnetic field amplitude across the length of dynamic magnetic stripe communications devices 805 and 830.
  • a single first magnet can be configured to bias one track of electromagnetic data in each of dynamic magnetic stripe communications devices 805 and 830.
  • a single first magnet may be configured to reduce or eliminate cross talk between different tracks of the electromagnetic data within dynamic magnetic stripe communications devices 805 and 830.
  • second magnets 815 and 835 may be a single magnet, e.g., to make handling and manufacturing easier. For example, using a single magnet may eliminate issue of manufacturing a device with two magnets whose magnetic poles are oriented in the same direction in proximity of each other.
  • a single second magnet may be configured to maintain a constant magnetic field amplitude across the length of dynamic magnetic stripe communications devices 815 and 835.
  • a single second magnet can be configured to bias one track of electromagnetic data in each of dynamic magnetic stripe communications devices 815 and 835.
  • a single second magnet may be configured to reduce or eliminate cross talk between different tracks of the electromagnetic data within dynamic magnetic stripe communications devices 815 and 835.
  • shield 820 may be placed between dynamic magnetic stripe communications devices 805, first magnets 810, and/or second magnets 815 and dynamic magnetic stripe communications devices 830, first magnets 825, and/or second magnets 835.
  • each of these elements function in the same manner as described above in relation to their respective dynamic magnetic stripe.
  • first sensor 840a and second sensor 840b may be operable to detect the presence of a read-head.
  • first sensor 840a and second sensor 840b may be operable to generate a voltage in relation to magnetic fields it experiences.
  • first sensor 840a and second sensor 840b may be Hall sensors, or other sensors that are affected by the "Hall effect.”
  • first sensor 840a and second sensor 840b may be configured to increase the voltage output when a magnetic read-head passes over the card.
  • first sensor 840a and second sensor 840b can be configured to generate a different change in voltage when a magnetic read-head passes under the card.
  • first sensor 840a and second sensor 840b may be configured to decrease the voltage output when a magnetic read-head passes under the card.
  • first sensor 840a and second sensor 840b may be configured to provide a specific voltage output when a magnetic read-head passes under the card at the same time as when a magnetic read-head passes over the card.
  • the device is able to determine if it should activate dynamic magnetic stripe 805, 830, or both.
  • the voltage increase or decrease may also be measured to identify the type of magnetic read-head, for example a shielded magnetic read-head.
  • the device may determine which direction it is being traveling, for example if it is being swiped through a payment reader. This will allow it to output data on dynamic magnetic stripe communications device 805, 830, or both in the appropriate order using the appropriate formatting.
  • a card for example card 100, may be provided without any activated products.
  • all displays may be blank and the card may be configured not to transmit any data.
  • the card may display a serial number, either printed on the card or displayed on one or more of the displays.
  • a user may use this serial number to receive a product activation code, for example by entering it into a web site, providing it to an authorized issuer in person, over the phone, or via text, or other manners known to a person of skill in the art.
  • cards can be manufactured without personal information and handed out at a variety of avenues such as launch parties, sports events, college campuses, etc. without requiring users to fill out application forms. Later information can be gathered from the user, for example when the serial number is entered. Alternatively, information can be entered earlier, for example due to previous interactions with the issuer, and the user can link this card, through the serial number, to an existing account.
  • a product activation code may be utilized to activate a product on the card.
  • the product may be stored on the card or other device (e.g., a mobile telephonic device) and may be inactive to authorize a purchase until activated.
  • This product activation code may be entered online via a website or on the card.
  • the code may be entered on the card manually (e.g., via a user interface) or via a wire-based or wireless connection (e.g., a wireless connection to a computer). Accordingly, the product may be activated on the card (or other device) or on a remote authorization server.
  • Product activation may occur in a variety of ways. Particularly, for example, an activation code received on a card may cause a processor to communicate product data via a communications device when a button associated with that product is pressed. For example, a payment card number associated with a product may be communicated through an RFID antenna, IC chip, and/or magnetic stripe communications device once the product is activated on card 100.
  • data associated with the product may be displayed on a display on card 100 after a product has been activated.
  • Product data may, for example, be pre-stored on a card when the card is mailed to a user.
  • An activation code may cause a particular product to be associated with a particular button (or manual interface input) and communicated through a communications device (e.g., a dynamic magnetic stripe communications device) when that button (or manual interface input) is provided by a user to a card.
  • An activation code may be received online, in a store, or over a phone to enter into a card.
  • a pre-stored product may be pre-associated to a particular button or may be associated to a particular button at activation.
  • a primary product e.g., a product the user desired to obtain and was mailed to a user
  • a non-activated product may also have printed information on the face of a card for online and phone purchases and may be associated with a button for in-store purchases, but may not communicate magnetic stripe information until the product is activated.
  • the product may have a verification code that displays on a display after product activation. Alternatively, for example, the activation code may be printed.
  • a card may have a plurality of buttons (e.g., two), but may have more non-activated products stored than buttons. In doing so, an issuer may be provided with a number of cross-selling opportunities.
  • buttons e.g., two
  • an issuer may be provided with a number of cross-selling opportunities.
  • a user activates a particular product, that product may be associated with a button.
  • the corresponding magnetic stripe data communicated through a dynamic magnetic stripe communications device may be communicated when the associated button is pressed by a user.
  • more products may be stored in a card in an inactivated state than there are buttons, or other manual user interface inputs, on a card.
  • An activated product may be associated with the next available button from a list of available buttons.
  • buttons next to these buttons may be utilized to, for example, indicate the payment product associated to the button.
  • a card may have a particular button for activating a product that may be pressed before an activation code is entered. In doing so, the processor of a card may determine when a code is desired to be entered by a user.
  • a product may be activated on a remote authorization server. Accordingly, a card may, for example, communicate data (e.g., via a magnetic stripe communications device) before a payment product is activated. Yet, the authorization of a payment associated with that payment product may not be authorized until the product is activated.
  • activation of the authorization may occur by having a user enter a code online or provide a code over the phone.
  • This code may be generated by a card via a display to identify the card and/or payment product.
  • a card may be provided to a user in a particular configuration.
  • the card may include multiple printed account numbers for both activated and non-activated products.
  • a button may be associated with each activated and non- activated product.
  • a user may activate a product online or via a telephone call. The user may identify himself/herself in a variety of ways such as, for example, answering a number of security questions, providing information about recent purchases, and/or providing particular passwords.
  • a card-generated and displayed activation code may also be utilized.
  • the product may be activated such that the product may be utilized to authorize purchase transactions. Accordingly, the product may be used online or offline before activation but not cause a purchase transaction to complete until the product is activated and remote authorization servers updated with product activation information.
  • Both a card and the authorization servers may, for example, be activated.
  • a user may press button 138 to receive an authorization activation code.
  • a user may provide this information to a remote server (e.g., either online or via an operator over the phone).
  • the user may receive an on- card product activation code from this remote server (e.g., via a webpage or via the operator over the phone).
  • the card may then receive this code to activate the product for the button and, for example, cause the next press of button 138 to display information associated with that product on display 125 (e.g., a payment card number) and communicate information associated with the product via one or more communication devices (e.g., RFID antennas, IC chips, or magnetic stripe communication devices).
  • communication devices e.g., RFID antennas, IC chips, or magnetic stripe communication devices.
  • the code may be received via manual input (e.g., manual input using buttons 130-134), wire-based input (e.g., USB) or wireless input (e.g., via light pulses, sound pulses, or other wireless communication signals).
  • a product that a user did not particularly request to be on a card may or may not require an activation code to initiate the product.
  • the additional product may be utilized by a user by, for example, entering manual input into the card indicative of a desire to use that additional product (e.g., pushing a mechanical button). Accordingly, a user may receive a mailing that includes a card with a payment product that a user requested as well as one or more products that the user did not request.
  • Such products may be pre-approved and may operate and authorize transactions without, for example, a particular activation code.
  • a card may include additional products that a user did not request, for example, where some of these additional products require an activation code and other of these additional products do not require an activation code.
  • Activation of inactivated products can be performed online via a webpage or over the phone via an operator without the actual use of an activation code.
  • a user may identify himself/herself by logging into an online account. The user may select a primary account associated with a card. The user may then be displayed with information associated with the additional products that were provided on the card. Accordingly, a user may select an activation button on the website to activate the product.
  • a card may generate (e.g., display) a code after a product is activated that may be provided back to a remote facility to confirm proper activation. Additionally, a card may generate a code via a communications device (e.g., a dynamic magnetic stripe device, RFID, or IC chip) such that an on-card activation verification code may be communicated with a user's first purchase.
  • a communications device e.g., a dynamic magnetic stripe device, RFID, or IC chip
  • Products that may be placed on a card may include, for example, debit products (e.g., decoupled or coupled debit products), credit products, gift products, pre-paid payment products, loyalty products, or any other type of product. Such products may each have a different number that is communicated via one or more reader communications devices (e.g., an RFID antenna, IC chip, or magnetic stripe communications device) as well as one or more displays.
  • debit products e.g., decoupled or coupled debit products
  • credit products e.g., gift products, pre-paid payment products, loyalty products, or any other type of product.
  • Such products may each have a different number that is communicated via one or more reader communications devices (e.g., an RFID antenna, IC chip, or magnetic stripe communications device) as well as one or more displays.
  • reader communications devices e.g., an RFID antenna, IC chip, or magnetic stripe communications device
  • a grocery store chain may provide users with a credit card that includes an inactivated loyalty number.
  • the loyalty number may be used to receive discounts and instant coupons at the grocery store chain.
  • a user may press a button, for example, associated with the credit card product to have a credit card number associated with that credit card product communicated via a communications device (e.g., a magnetic stripe communications device).
  • a user may press a different button, for example, associated with the loyalty product, to have the loyalty number associated with the loyalty product, communicated via a communications device (e.g., that same magnetic stripe communications device).
  • the credit card product may be a default product that automatically communicates the credit card number associated with the default credit card product whenever the card is utilized without additional manual input.
  • a user may log into his/her online account for the credit card product and may activate the loyalty card.
  • the user may change/replace the number by changing the number online via the website and being provided with a code to enter into the card to change/replace the product (e.g., via manual input, light, sound, or a wireless or wire-based communications signal).
  • Incentives to activate a product may be provided to a user.
  • incentives may be displayed online (e.g., via a webpage displaying the products to- be-activated) or on-card.
  • a user may press a button associated with an inactivated card and may be provided with an incentive on a display.
  • a user may be provided with text indicating that if the user activates the product within a period of time (e.g., within the next 10 days) then an amount of money may be added to a user's account.
  • a card may provide an activation code that includes embedded information indicative of the incentive.
  • An incentive code (e.g., promotional code) may also be displayed to a user. Incentives may be displayed based on time. For example, one incentive may be displayed during the first 10 days a card is used by a user and a different incentive may be displayed during the next 10 days a card is used by a user. After all incentives are exhausted, for example, a card may erase the new product so that the product is removed from a card. An incentive and/or new product may be erased after a period of time or upon a card receiving manual input from a user indicative of a user's desire to erase the product and/or incentive.
  • multiple new products may be stored on the card and rotated such that different new products may be displayed to a user.
  • a display may be provided next to a button and the name of the new product may be displayed on such a display.
  • a user may navigate through possible new products and may select, on card 100, the product or products the user desires.
  • a user may erase products the user does not desire from a memory of card 100.
  • FIG. 57 shows network topology 900 that may include, for example, mobile device 902 (e.g., a mobile telephonic device, a PDA, an electronic tablet, a laptop, a GPS unit, or an MP3 player).
  • Mobile device 902 may, for example, include a contactless interface that may initiate, sustain, and/or terminate communication channel 926 between card 904 and mobile device 902.
  • Card 904 and mobile device 902 may communicate via channel 926 via a contactless communication medium (e.g., an RF medium).
  • a contactless communication medium e.g., an RF medium
  • Mobile device 902 may provide one or more transceivers that may communicate with one or more wired networks (e.g., IP network 912 and/or payment network 914) and/or one or more wireless networks (e.g., mobile network 910).
  • Mobile device 902 may, for example, communicate with a cellular station over a wireless radio interface (e.g., a GSM air interface) that may be used by mobile device 902 to communicate information (e.g., voice and data) to cellular network access infrastructure 906 (e.g., one or more GSM base transceiver stations, base station controllers, and mobile switching centers).
  • a wireless radio interface e.g., a GSM air interface
  • information e.g., voice and data
  • cellular network access infrastructure 906 e.g., one or more GSM base transceiver stations, base station controllers, and mobile switching centers.
  • cellular network access infrastructure 906 may utilize any multiple access architecture, such as for example, a code-division multiple access architecture and/or a time-division multiple access architecture.
  • Mobile device 902 may, for example, communicate with wireless access point 908 over a wireless interface (e.g., a Bluetooth interface or a Wi-Fi interface). Accordingly, for example, mobile device 902 may access one or more wired networks (e.g., IP network 912 and/or payment network 914) and/or one or more wireless networks (e.g., mobile network 910) without the need to first gain access to cellular network access infrastructure 906.
  • a wireless interface e.g., a Bluetooth interface or a Wi-Fi interface
  • wired networks e.g., IP network 912 and/or payment network 914
  • wireless networks e.g., mobile network 910
  • Card 904 may, for example, be a powered card or a non-powered card (e.g., a powered payment card or a non-powered payment card). Accordingly, for example, payment information (e.g., a payment account number and a card expiration date) may be communicated from card 904 to mobile device 902 in support of a financial transaction being conducted by mobile device 902. In so doing, for example, items for purchase on IP network 912 (e.g., the internet) may be accessed by a browser of mobile device 902 via an access point (e.g., wireless access point 908 or cellular network access infrastructure 906). Mobile device 902 may, for example, complete a purchase transaction by first obtaining required payment information from card 904 and then communicating such payment information to network entities (e.g., payment server 916 and/or issuer 920).
  • network entities e.g., payment server 916 and/or issuer 920.
  • Payment server 916 may, for example, contact issuer 920 via a network (e.g., payment network 914) with payment information received from mobile device 902 for authorization of a purchase. Once authorized, payment transaction information may be recorded onto a receipt that may be delivered to mobile device 902 via any one or more delivery options (e.g., via a short messaging service of mobile network 910 or an email delivery service of IP network 912). Mobile device 902 may allow a user to associate purchase categories (e.g., groceries, auto repair, or entertainment) to purchases transacted by the mobile device so that the user may receive a more detailed accounting of his or her expenditures on his or her receipt.
  • purchase categories e.g., groceries, auto repair, or entertainment
  • a payment receipt may, for example, be provided to mobile device 902 as a proof-of-purchase object (e.g., a barcode) that may be provided to a display of mobile device 902 and read by other computing equipment (e.g., a barcode scanner) for proof-of-purchase confirmation.
  • a proof-of-purchase object e.g., a barcode
  • other computing equipment e.g., a barcode scanner
  • a device may, for example, include a contactless communication device (e.g., an RFID device) that may initiate, sustain, and/or terminate a contactless communication channel (e.g., an RFID communications channel) with merchant terminal 918.
  • a contactless communication device e.g., an RFID device
  • card 922 and/or mobile device 928 may communicate payment information to merchant terminal 918 to complete a financial transaction.
  • mobile device 928 and/or card 922 may first receive a request from a user to communicate payment information to merchant terminal 918.
  • a user of card 922 may press a button on card 922 that may cause payment information to be transferred to a memory of a processor (e.g., an RFID chip).
  • An associated RFID antenna may, for example, sense the presence of merchant terminal 918 by detecting an RF carrier field that may be generated by an RFID device of merchant terminal 918. Once the presence of merchant terminal 918 is sensed, payment information may be transferred from an RFID chip of card 922 to an RFID antenna of card 922 to communicate the payment information via an RFID communication channel to merchant terminal 918 to complete a financial transaction.
  • card 922 may be a non-powered card (e.g., a non-powered payment card).
  • card 922 may include an RFID chip and associated RFID antenna that may be brought within proximity to merchant terminal 918.
  • An RFID antenna of card 922 may sense an RF carrier field generated by merchant terminal 918 and may derive operational power from the RF carrier field. The operational power may, for example, be collected by an RFID antenna of card 922 and provided to an associated RFID chip of card 922 in order to energize the RFID chip of card 922.
  • an RFID chip of card 922 may modulate an RF carrier field generated by merchant terminal 918 to, for example, communicate payment information from card 922 to merchant terminal 918 to complete a purchase transaction.
  • Any computing device may, for example, provide contactless communication electronics (e.g., an RFID reader) that may communicate with a contactless communication device (e.g., card 932 and/or mobile device 934).
  • contactless communication electronics e.g., an RFID reader
  • a contactless communication device e.g., card 932 and/or mobile device 934.
  • any information that may be communicated by card 932 may be received by computing device 930 (e.g., received via an RFID communication channel established between card 932 and computing device 930) and forwarded onto a network entity (e.g., issuer 920 and/or payment server 916) to complete a purchase transaction.
  • a network entity e.g., issuer 920 and/or payment server 916
  • RFID information may be exchanged between computing device 930 and an RFID enabled device (e.g., card 932 and/or mobile device 934).
  • FIG. 58 shows mobile device 1000.
  • Mobile device 1000 may be any mobile device, such as a mobile telephonic device (e.g., cell phone), a PDA, an electronic tablet, an MP3 player, or a locating device (e.g., a GPS device). Accordingly, mobile device 1000 may be operated in a mobile environment while a user of mobile device 1000 goes about his or her daily activities (e.g., driving, shopping, walking, dining, and exercising). In addition, for example, mobile device 1000 may perform multiple functions simultaneously (e.g., a person may carry on a conversation while at the same time browsing and purchasing products on the internet).
  • Mobile device 1000 may include audio processing devices (e.g., microphone 1008 and speaker 1010). Accordingly, for example, mobile device 1000 may receive voice commands from a user via microphone 1008 and may process such commands to perform a function. For example, a user may place mobile device 1000 into a desired operational mode by speaking a command into microphone 1008 that is associated with the desired operational mode. In so doing, for example, mobile device 1000 may engage in hands-free operation by receiving voice commands via microphone 1008 and performing functions associated with the received voice commands.
  • Mobile device 1000 may receive data input via microphone 1008. For example, a voice-band modem may generate signals in a voice-band frequency range that may be received by microphone 1008. A processor of mobile device 1000 may interpret the received audible information as data signals and may process the data signals as, for example, data values and/or control data input.
  • Mobile device 1000 may include camera 1002. Camera 1002 may capture one or more frames of video data and store the video data within a memory of mobile device 1000. Accordingly, for example, a processor of mobile device 1000 may receive one or more frames of video information via camera 1002 and may process the video information as data values and/or control data input. In so doing, for example, mobile device 1000 may receive optical information that is sensed by camera 1002 during a series of one or more video capture events that produce one or more frames of video information. The one or more frames of video information may contain one or more data elements (e.g., pixels) having properties (e.g., color, intensity, or contrast) that may be interpreted by a processor of mobile device 1000 as data values and/or control data.
  • data elements e.g., pixels
  • properties e.g., color, intensity, or contrast
  • Mobile device 1000 may include manual input interface 1012.
  • Manual input interface 1012 may, for example, include keys and/or buttons that may be sensitive to manual input, such as a touch or an application of pressure. Accordingly, for example, a user of mobile device 1000 may enter information into mobile device 1000 via manual interface 1012 to cause a processor of mobile device 1000 to enter a particular mode of operation.
  • Manual interface 1012 may, for example, be used for data entry (e.g., dialing a phone number or entering data as may be requested by mobile device 1000) during a particular mode of operation of mobile device 1000.
  • Mobile device 1000 may include display 1004.
  • Display 1004 may provide visible information that may be utilized by a user during interaction with mobile device 1000.
  • a portion or all of display 1004 may be touch sensitive such that objects making contact with display 1004 or objects coming within a proximity of display 1004 may be detected by a processor of mobile device 1000.
  • RFID operations graphical user interface 1006 may be provided by display 1004 so that graphical information may be displayed to solicit and/or receive data entry from a user.
  • touch-sensitive graphical user interface devices such as radio buttons, textual input boxes, virtual buttons, pull-down menus, and navigational tools may be used for data entry to initiate, change, and/or support functions performed by mobile device 1000.
  • FIG. 10 shows architecture 1050.
  • User interface 1052 may, for example, be included within architecture 1050 to allow user interaction with architecture 1050.
  • a dedicated key pad or keyboard may be included within user interface 1052 to allow alphanumeric data entry into architecture 1050.
  • Architecture 1050 may include one or more displays 1054.
  • Display 1054 may, for example, be touch-sensitive. Accordingly, for example, display 1054 may be utilized for alphanumeric data entry using virtual buttons that may be rendered onto touch- sensitive portions of display 1054. In so doing, for example, touching virtual buttons that may be associated with alphabetic and numeric characters of display 1054 may be detected by processor 1058 as alphanumeric data entry.
  • Alphanumeric entry boxes may, for example, be rendered onto display 1054.
  • a user may, for example, activate a cursor within such an alphanumeric entry box by touching an area within the alphanumeric entry box.
  • a user may utilize user interface 1052 and/or a virtual keypad rendered onto display 1054 to select alphanumeric characters to be placed within the alphanumeric entry box in accordance with a character position identified by an activated cursor within the alphanumeric entry box.
  • processor 1058 may receive alphanumeric characters as typed into a alphanumeric entry box of display 1054 and may use such alphanumeric characters as data input.
  • Display 1054 may, for example, provide data output from architecture 1050.
  • display 1054 may communicate data using a series of light pulses.
  • processor 1058 may cause one or more portions of display 1054 to produce light pulses having varying characteristics (e.g., duration, intensity, and frequency) that may communicate information via such light pulses.
  • a device that may be sensitive to light pulses may receive information communicated by display 1054 via light pulses having varying characteristics.
  • Display 1054 may, for example, communicate data using visual information that may be substantially static (e.g., a barcode).
  • Architecture 1050 may include one or more transceivers 1056.
  • Transceiver 1056 may communicate information to and/or may receive information from one or more devices. Transceiver 1056 may, for example, communicate via a wireless interface with one or more cellular stations of a mobile network. Accordingly, for example, transceiver 1056 may allow a mobile device (e.g., mobile device 1000 of FIG. 10) to establish a communications channel with an associated cellular station. In so doing, for example, a mobile device (e.g., mobile device 1000 of FIG. 10) may exchange information (e.g., voice, text, data, or multimedia) with one or more terrestrial networks (e.g., the internet or a payment network) via an associated cellular station. As per another example, transceiver 1056 may exchange information with one or more other mobile devices via one or more associated cellular stations.
  • a mobile device e.g., mobile device 1000 of FIG. 10
  • information e.g., voice, text, data, or multimedia
  • terrestrial networks e.g., the internet or a payment network

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Theoretical Computer Science (AREA)
  • Finance (AREA)
  • General Business, Economics & Management (AREA)
  • Development Economics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Economics (AREA)
  • Computer Security & Cryptography (AREA)
  • Microelectronics & Electronic Packaging (AREA)
  • Marketing (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Game Theory and Decision Science (AREA)
  • Cash Registers Or Receiving Machines (AREA)

Abstract

Une carte de portefeuille ou un autre dispositif comprend trois boutons, une antenne PCB destinée à une connexion à toutes les bandes cellulaires y compris bande basse, bande moyenne et bande haute, des capteurs à double pression permettant de déterminer la vitesse et/ou en tant que déclencheur indépendant, une puce cellulaire dont la clé de chiffrement/déchiffrement entre un réseau de paiement et la puce cellulaire est dynamiquement modifiable pour la sécurité, et un dispositif de communication magnétique dynamique permettant de communiquer des données à l'aide d'une forme d'onde de données magnétiques dont l'amplitude est réglée par le dispositif.
PCT/IB2020/000934 2020-10-06 2020-10-06 Cartes, dispositifs, systèmes et procédés destinés à la sélection de fonctionnalités de paiement avancées WO2022074416A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/IB2020/000934 WO2022074416A1 (fr) 2020-10-06 2020-10-06 Cartes, dispositifs, systèmes et procédés destinés à la sélection de fonctionnalités de paiement avancées

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2020/000934 WO2022074416A1 (fr) 2020-10-06 2020-10-06 Cartes, dispositifs, systèmes et procédés destinés à la sélection de fonctionnalités de paiement avancées

Publications (1)

Publication Number Publication Date
WO2022074416A1 true WO2022074416A1 (fr) 2022-04-14

Family

ID=81126597

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2020/000934 WO2022074416A1 (fr) 2020-10-06 2020-10-06 Cartes, dispositifs, systèmes et procédés destinés à la sélection de fonctionnalités de paiement avancées

Country Status (1)

Country Link
WO (1) WO2022074416A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220335519A1 (en) * 2021-04-16 2022-10-20 Gbt Technologies Inc. Consolidated credit cards, automated billing systems, and financial technologies for improved credit card account operations

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160307189A1 (en) * 2011-10-17 2016-10-20 Capital One Services, LLC. System, method, and apparatus for a dynamic transaction card
US20190303945A1 (en) * 2015-03-13 2019-10-03 Radiius Corp Smartcard Payment System and Method
US20190340398A1 (en) * 2016-08-16 2019-11-07 Cpi Card Group - Colorado, Inc. Improved ic chip card
US20190392424A1 (en) * 2016-12-19 2019-12-26 Xard Group Pty Ltd. Digital transaction apparatus, system, and method with a virtual companion card

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160307189A1 (en) * 2011-10-17 2016-10-20 Capital One Services, LLC. System, method, and apparatus for a dynamic transaction card
US20190303945A1 (en) * 2015-03-13 2019-10-03 Radiius Corp Smartcard Payment System and Method
US20190340398A1 (en) * 2016-08-16 2019-11-07 Cpi Card Group - Colorado, Inc. Improved ic chip card
US20190392424A1 (en) * 2016-12-19 2019-12-26 Xard Group Pty Ltd. Digital transaction apparatus, system, and method with a virtual companion card

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220335519A1 (en) * 2021-04-16 2022-10-20 Gbt Technologies Inc. Consolidated credit cards, automated billing systems, and financial technologies for improved credit card account operations

Similar Documents

Publication Publication Date Title
US20210110391A1 (en) Advanced secure payment device
US11144909B1 (en) Cards deployed with inactivated products for activation
US9704089B2 (en) Systems and methods for programmable payment cards and devices with loyalty-based payment applications
US8622309B1 (en) Payment cards and devices with budgets, parental controls, and virtual accounts
US20160335531A1 (en) Dynamic security codes, tokens, displays, cards, devices, multi-card devices, systems and methods
US20120254037A1 (en) Cards, devices, systems, and methods for payment functionality selection
CA2835508A1 (fr) Systemes, dispositifs et procedes pour une acceptation de paiement mobile, des autorisations mobiles, des portefeuilles mobiles et des mecanismes de communication sans contact
AU2020200939B2 (en) Cards and devices with magnetic emulators for communicating with magnetic stripe readers and applications for the same
WO2022074416A1 (fr) Cartes, dispositifs, systèmes et procédés destinés à la sélection de fonctionnalités de paiement avancées
US20200342446A1 (en) Super smart secure payment applets with pre-stored messages and logic and ability to change subsequent function thereon
US11126997B1 (en) Cards, devices, systems, and methods for a fulfillment system
AU2017204011A1 (en) Systems, devices, and methods for mobile payment acceptance, mobile authorizations, mobile wallets, and contactless communication mechanisms
AU2016201777B2 (en) Cards and devices with magnetic emulators for communicating with magnetic stripe readers and applications for the same

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20956629

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20956629

Country of ref document: EP

Kind code of ref document: A1