SYSTEMS AND METHODS FOR TRANSACTION DETECTION AND TRANSACTION INDICATOR MECHANISMS FOR CARDS AND DEVICES

Information

  • Patent Application
  • 20210110370
  • Publication Number
    20210110370
  • Date Filed
    October 06, 2020
    3 years ago
  • Date Published
    April 15, 2021
    3 years ago
Abstract
A detection activity of a card may be sensitive to property changes in one or more conductive pads on the card and/or information received by the card, where a processor of the card may execute a transaction indication algorithm based on detected property changes on the card, that may be caused by the card's proximity to a point-of-sale terminal and/or by information received by the card. The transaction indication algorithm may cause the processor to provide visible, audible and/or tactile indicators on the card based on the detection.
Description
BACKGROUND OF THE INVENTION

his invention relates to cards and devices and related systems, and card indicator systems.


SUMMARY OF THE INVENTION

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, for example, 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.


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)). 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. For example, 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. For example, an integrated circuit (IC) may be included on a card and exposed from the surface of the card. Such a chip (e.g., an EMV 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). 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. For example, a detected object may include a determination that the object is a read-head housing of a magnetic stripe reader. Such an identifying detection, for example, 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. Alternately, 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, for example, 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) 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. In doing so, for example, a series of detections (e.g., the capacitance magnitude of a series of conductive pads may increase and/or decrease) which may be indicative of a direction of a card swipe, a velocity of a card swipe and/or an acceleration of a card swipe.


A processor of the card may activate a transaction indicator (e.g., a visible or audible indicator) that is indicative of a completed transaction. For example, 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. In so doing, 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. In addition, 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. For example, certain objects (e.g., a finger) may cause a processor of a card to detect, for example, a presence of a read-head housing of a magnetic stripe reader when, in fact, no read-head housing is present. In such instances, 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 200, or any number of LEDs.


According to example embodiments, 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. As another example, when 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×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. 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.


According to some example embodiments, a metal card or other device may be improved, for example, with precious metals and mirror finishes. For example, 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. For example, 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.


According to some example embodiments, a mask may be provided, for example, by using resist based processes and/or stickers. For example 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.


After metal deposition, a clear or colored plastic layer may be applied. For example, 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. Similarly, 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.


According to some example embodiments, a skin layer or other layer (e.g., a plastic layer) may be etched with a pattern prior to metal deposition to provide an inlay. According to some example embodiments, a skin layer or other layer (e.g., a plastic layer) may be etched with a pattern prior to metal deposition and a mask (e.g., sticker) applied to provide an inlay and protrusion on the card to provide a three dimensional image with metal above and below the skin layer surface. According to some example embodiments, mechanical engraving may be performed.





BRIEF DESCRIPTION OF THE DRAWINGS

The principles and advantages of the present invention can be more clearly understood from the following detailed description considered in conjunction with the following drawings, in which the same reference numerals denote the same structural elements throughout, and in which:



FIG. 1 is an illustration of a card constructed in accordance with the principles of the present invention;



FIG. 2 is an illustration of a card constructed in accordance with the principles of the present invention;



FIG. 3 is an illustration of circuitry, and associated waveforms, constructed in accordance with the principles of the present invention;



FIG. 4 is an illustration of a card constructed in accordance with the principles of the present invention;



FIG. 5 is an illustration of a card constructed in accordance with the principles of the present invention;



FIG. 6 is an illustration of a card constructed in accordance with the principles of the present invention;



FIG. 7 is an illustration of process flow charts constructed in accordance with the principles of the present invention;



FIG. 8 is an illustration of a card constructed in accordance with the principles of the present invention;



FIG. 9 is an illustration of a card constructed in accordance with the principles of the present invention; and



FIG. 10 is an illustration of a card constructed in accordance with the principles of the present invention.





DETAILED DESCRIPTION OF THE INVENTION


FIG. 1 shows card 100 that may include, for example, a dynamic number that may be entirely, or partially, displayed using a display (e.g., display 106). A dynamic number may include a permanent portion such as, for example, permanent portion 104 and a dynamic portion such as, for example, dynamic portion 106. Card 100 may include a dynamic number having permanent portion 104 and permanent portion 104 may be incorporated on card 100 so as to be visible to an observer of card 100. For example, labeling techniques, such as printing, embossing, laser etching, etc., may be utilized to visibly implement permanent portion 104.


Card 100 may include a second dynamic number that may be entirely, or partially, displayed via a second display (e.g., display 108). Display 108 may be utilized, for example, to display a dynamic code such as a dynamic security code. Card 100 may include third display 122 that may be used to display graphical information, such as logos and barcodes. Third display 122 may be utilized to display multiple rows and/or columns of textual and/or graphical information.


Persons skilled in the art will appreciate that any one or more of displays 106, 108, and/or 122 may be implemented as a bi-stable display. For example, information provided on displays 106, 108, and/or 122 may be stable in at least two different states (e.g., a powered-on state and a powered-off state). Any one or more of displays 106, 108, and/or 122 may be implemented as a non-bi-stable display. For example, the display is stable in response to operational power that is applied to the non-bi-stable display. Other display types, such as LCD or electro-chromic, may be provided as well.


Other permanent information, such as permanent information 120, may be included within card 100, which may include user specific information, such as the cardholder's name or username. Permanent information 120 may, for example, include information that is specific to card 100 (e.g., a card issue date, a card expiration date, a network logo and/or indicia associated with an issuer of card 100). Information 120 may represent, for example, information that includes information that is both specific to the cardholder, as well as information that is specific to card 100. Light sources (not shown) may be provided proximate to permanent information 120 and may be activated and deactivated to highlight at least a portion of permanent information 120.


Card 100 may accept user input data via any one or more data input devices, such as buttons 110-118. Buttons 110-118 may be included to accept data entry through mechanical distortion, contact, or proximity. Buttons 110-118 may be responsive to, for example, induced changes and/or deviations in light intensity, pressure magnitude, or electric and/or magnetic field strength. Such information exchange may then be determined and processed by a processor of card 100 as data input.


Detectors 124 may be implemented to detect, for example, the proximity, or actual contact, of an object (e.g., a read-head housing of a magnetic stripe reader, an EMV reader or a bar code reader). Proximity detectors 124 may be utilized, for example, to detect a magnetic stripe reader during a transaction (e.g., a card-based financial transaction) when card 100 is swiped through a read-head housing of the magnetic stripe reader. During such a transaction, dynamic magnetic stripe communications device 102 may be activated in response to such a detection to provide one or more tracks of magnetic stripe data to the detected magnetic stripe reader. Alternately, a static magnetic stripe (not shown) and/or a dynamic magnetic stripe communications device may be used to provide one or more tracks of magnetic stripe data to the detected magnetic stripe reader. In other alternatives, an EMV chip, an RFID device and/or an electromagnetic device may be used to exchange transaction data with the detected EMV reader, RFID reader and/or magnetic stripe reader, respectively.


Once a point-of-sale terminal is detected, one or more visible indicators (e.g., LEDs) and/or an audible indicator (e.g., a speaker) and/or a tactile indicator (e.g., a vibrator) on a card may be activated in accordance with a transaction indicator algorithm to provide visible and/or audible and/or tactile feedback as to the occurrence of a transaction completed by card 100 and the associated point-of-sale terminal. Alternately, some other usage of card 100 (e.g., replenishment of credit onto a reloadable gift card) may also be indicated by activation of a transaction indicator algorithm.


Card 100 may be implemented using architecture 150, which may include one or more processors 154. One or more processors 154 may be configured to utilize external memory 152, internal memory of processor 154, or a combination of external memory 152 and internal memory for storing information, such as executable machine language, related dynamic machine data, transaction indicator algorithms and user input data values.


One or more of the components shown in architecture 150 may be configured to transmit information to processor 154 and/or may be configured to receive information as transmitted by processor 154. For example, one or more displays 156 may be coupled to receive data from processor 154. The data received from processor 154 may include, for example, at least a portion of dynamic numbers and/or dynamic codes. The data to be displayed on the display may be displayed on one or more displays 156.


One or more displays 156 may be, for example, touch sensitive and/or proximity sensitive. For example, objects such as fingers, pointing devices, etc., may be brought into contact with displays 156, or in proximity to displays 156. Detection of object proximity or object contact with displays 156 may be effective to perform any type of function (e.g., transmit data to processor 154). Displays 156 may have multiple locations that are able to be determined as being touched, or determined as being in proximity to an object.


Input and/or output devices may be implemented on architecture 150. For example, integrated circuit (IC) chip 160 (e.g., an EMV chip) may be included on architecture 150, that can exchange information with a chip reader (e.g., an EMV chip reader). Radio frequency identification (RFID) module 162 may be included within architecture 150 to enable the exchange of information with an RFID reader.


Other input and/or output devices 168 may be included on architecture 150, for example, to provide any number of input and/or output capabilities. For example, other input and/or output devices 168 may include an audio device capable of receiving and/or transmitting audible information.


Other input and/or output devices 168 may include a device that exchanges analog and/or digital data using a visible data carrier. Other input and/or output devices 168 may include a device, for example, that is sensitive to a non-visible data carrier, such as an infrared data carrier or electromagnetic data carrier. Other input and/or output devices 168 may include a device, for example, that is sensitive to laser light, such as light generated by a barcode scanner.


Persons skilled in the art will appreciate that a card (e.g., card 100 of FIG. 1) may, for example, be a self-contained device that derives its own operational power from one or more batteries 158. Furthermore, one or more batteries 158 may be included, for example, to provide operational power for a period of time (e.g., approximately 2-4 years). One or more batteries 158 may be included, for example, as rechargeable batteries.


Electromagnetic field generators 170-174 may be included on architecture 150 to communicate information to, for example, a read-head of a magnetic stripe reader via, for example, electromagnetic signals. For example, electromagnetic field generators 170-174 may be included to communicate one or more tracks of electromagnetic data to read-heads of a magnetic stripe reader. Electromagnetic field generators 170-174 may include, for example, a series of electromagnetic elements, where each electromagnetic element may be implemented as a coil wrapped around one or more materials (e.g., a magnetic material and/or a non-magnetic material). Additional materials may be placed outside the coil (e.g., a magnetic material and/or a non-magnetic material).


Electrical excitation by processor 154 of one or more coils of one or more electromagnetic elements via, for example, driving circuitry 164 may be effective to generate electromagnetic fields from one or more electromagnetic elements. One or more electromagnetic field generators 170-174 may be utilized to communicate electromagnetic information to, for example, one or more read-heads of a magnetic stripe reader. Alternately, a static magnetic stripe (not shown) may be used by itself, or in combination with electromagnetic field generators 170-174, to communicate information to a magnetic stripe reader.


Timing aspects of information exchange between the various I/O devices implemented on architecture 150 may be determined by processor 154.


One or more proximity detectors 166 may be utilized, for example, to sense the proximity, mechanical distortion, or actual contact, of an external device, which in turn, may trigger the initiation of a communication sequence by processor 154. The sensed presence, mechanical distortion, or touch of the external device may be effective to, for example, determine the type of device or object detected.


For example, the detection may include the detection of, for example, a point-of-sale terminal (e.g., a magnetic stripe reader, an EMV reader, an RFID reader, and a barcode scanner). In response, processor 154 may activate one or more communication devices to initiate a communications sequence with, for example, one or more point-of-sale terminals.


A transaction indicator algorithm may be executed by processor 154, for example, to cause the activation of a transaction indicator (e.g., light sources 176) when a point-of-sale terminal is detected. For example, after a card (e.g., card 100 of FIG. 1) is detected as having been swiped through a magnetic stripe reader, light sources 176, or other indicia such as audible or tactile indicia, may be activated by processor 154 in such a manner as to alert the card holder and others around the card holder that the card has just been used in a transaction. Alternately, for example, other I/O 168 may detect light emitted from a barcode scanner, which would then cause processor 154 to activate light sources 176, or other indicia such as audible or tactile indicia, in such a manner as to alert the card holder and others around the card holder that the card has just been used in a transaction. Still other transactions (e.g., transactions between IC chip 160 and an EMV reader or transactions between RFID 162 and an RFID reader) may cause processor 154 to activate light sources 176, or other indicia such as audible or tactile indicia, in such a manner as to alert the card holder and others around the card holder that the card has just been used in a transaction.


Turning to FIG. 2, a card is shown having an orientation of detectors 226, whereby one or more detectors 202-216 may be, for example, arranged along a length of card 200. Detectors 202-216 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 202-216 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 202-216 as may be required by a particular application.


Detection circuitry 220 of processor 218, conductive pads 202-216, processor 218, transaction indicator algorithm 230 and transaction indicator device 232 may be combined to provide a detection system. Persons skilled in the art will appreciate that any number of conductive pads may be utilized by a processor as capacitive sensing pads. Particularly, a processor may include the functionality to control a detection system to determine when an object is in the proximity of one or more conductive pads via a capacitive sensing technique.



FIG. 3 shows detection circuitry 300. 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.


A conductive pad may, for example, form a portion of a capacitive element, such that plate 316 of capacitive element 314 may be implemented by a conductive pad and the second plate of capacitive element 314 may be implemented by element 310. Element 310 may represent, for example, the device or object whose proximity or contact is sought to be detected.


The capacitance magnitude of capacitive element 314 may exhibit, for example, an inversely proportional relationship to the distance separation between plate 316 and device 310. For example, the capacitance magnitude of capacitive element 314 may be relatively low when the corresponding distance between plate 316 and device 310 may be relatively large. The capacitance magnitude of capacitive element 314 may be relatively large, for example, when the corresponding distance between plate 316 and device 310 is relatively small.


Detection may be accomplished, for example, via circuit 300 of FIG. 3. Through a sequence of charging and/or discharging events, a capacitance magnitude change for capacitive element 314 may be monitored over a given period of time. In so doing, for example, the spatial relationship (e.g., the separation distance) between plate 316 and device 310 may be approximated.


Charge sequence 350 may, for example, be optionally invoked, such that charge circuit 304 may be activated at time T1, while discharge circuit 306 may remain deactivated. Accordingly, for example, current may flow through resistive component 308. In doing so, for example, an electrostatic field may be generated that may be associated with capacitive component 314. During the charge sequence, for example, the voltage at node 312 may be monitored to determine the amount of time required (e.g., TCHARGE1−T1) for the voltage at node 312, V312, to obtain a magnitude that is substantially equal to, below, or above a first threshold voltage (e.g., equal to V1).


Discharge sequence 360 may, for example, be optionally invoked, such that discharge circuit 306 may be activated at time T2, while charge circuit 304 may remain deactivated. During the discharge sequence, for example, the electric field associated with capacitive element 314 may be allowed to discharge through resistive component 308 to a reference potential (e.g., ground potential). The voltage at node 312 may be monitored to determine the amount of time required (e.g., TDISCHARGE2−T2) for the voltage at node 312, V312, to obtain a magnitude that is substantially equal to, below, or above a second threshold voltage (e.g., equal to V2).


Once the charge time, TCHARGE, and/or discharge time, TDISCHARGE, are determined, the charge and/or discharge times may be utilized to calculate a capacitance magnitude that may be exhibited by capacitive element 314. For example, given that the magnitude of voltage, V1, may be equal to approximately 63% of the magnitude of voltage, Vs, then a first relationship may be defined by equation (1) as:






T
CHARGE
=R
308
*C1,   (1)


where R308 is the resistance magnitude of resistive element 308 and C1 is proportional to a capacitance magnitude of a capacitive element (e.g., capacitive element 314).


Similarly, for example, given that the magnitude of voltage, V2, is equal to approximately 37% of the magnitude of voltage, Vs, then a second relationship may be determined by equation (2) as:






T
DISCHARGE
=R
308
*C2,   (2)


where C2 is proportional to a capacitance magnitude of capacitive element 314. The capacitance magnitudes, C1 or C2, may then be calculated from equations (1) or (2), respectively, and taken by themselves to determine a capacitance magnitude that may be exhibited by capacitive element 314. Alternatively, for example, capacitance magnitudes, C1 and C2, may be calculated from equations (1) and (2), respectively, and averaged to determine a capacitance magnitude that may be exhibited by capacitive element 314.


Persons skilled in the art will appreciate that circuits 304 and/or 306 may be activated and deactivated by controller 320. Accordingly, for example, controller 320 may control when the charge and/or discharge events occur. Persons skilled in the art will further appreciate that controller 320 may adjust a frequency at which circuits 304 and 306 may be activated and/or deactivated, thereby adjusting a sampling rate at which the capacitance magnitudes, C1 and/or C2, may be measured.


Turning back to FIG. 2, a series of charge and/or discharge cycles for pads 202-216 may be executed by processor 218 to determine, for example, a relative capacitance magnitude that may be exhibited by each of pads 202-216. A series of charge and/or discharge cycles for each of pads 202-216 may be executed by processor 218, for example, in order to obtain a capacitance characteristic for each of pads 202-216 over time, thereby determining whether an object (e.g., a read-head housing of a magnetic stripe reader) is within a proximity to card 200, whether that object is moving with respect to card 200 and if so, what direction that object is moving and/or whether that object is accelerating with respect to card 200.


By comparing the time-based capacitance characteristic of each pad 202-216 to a threshold capacitance value, a determination may be made, for example, as to when pads 202-216 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 202-208, respectively, and/or pads 216-210, respectively, may be detected and a determination may be made that a device is moving substantially in direction 222 relative to card 200. A sequential change (e.g., increase) in the relative capacitance magnitudes of detectors 210-216, respectively, and/or 208-202, respectively, may be detected, for example, and a determination may be made that a device is moving substantially in direction 224 relative to card 200.


Persons skilled in the art will appreciate that by electrically shorting pairs of detectors together (e.g., pair 202/210, pair 204/212, pair 206/214, etc.) directional vectors 222 and 224 become insubstantial. For example, regardless of whether a device is moving substantially in direction 222 or substantially in direction 224 relative to card 200, a determination may nevertheless be made that a device is close to, or touching, card 200.


Detection circuitry 220 of processor 218 may be used in conjunction with, for example, one or more pads 202-216 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 202-216. Processor 218 may, for example, conclude that card 200 has been used in a transaction based on the detection and may execute transaction indicator algorithm 230 to determine the manner in which transaction indicator device 232 is to be activated based on the detected transaction (e.g., activation of one or more light sources, playing of a tune via an audible device, or vibration of card 200 via a tactile device).



FIG. 4 shows card 400 having front side 410 and back side 412. Card 400 may, for example, include a processor (not shown), a battery (not shown), a proximity detector (not shown) and memory to store a transaction indication algorithm to be executed by the processor. Front side 410 of card 400 may further include indicia 404 that may be indicative of a merchant who may honor card 400 at its point-of-sale terminal, indicia 406 that may be indicative of a payment network associated with card 400, indicia 408 that may be indicative of a payment account number (e.g., a gift card account number) that may be associated with a cash balance of card 400 with which to charge purchases against and design indicia 418 that may be printed or laser etched onto card 400.


Card 400 may, for example, be swiped through a magnetic stripe reader located at a point-of-sale terminal associated with merchant 404 and such a swipe may be detected by proximity detectors (not shown) of card 400. Based on the detection of the magnetic stripe reader and based on a transaction indication algorithm executed by the processor (not shown) of card 400, a visible indication of the transaction may be displayed by card 400. For example, one or more LEDs 402 may be illuminated based on the detection, such that LEDs may be illuminated to emit a constant intensity of light, varying intensities of light, a constant duration of light, a varying duration of light, a constant color of light, varying colors of light or any other form of light that may indicate that card 400 has been swiped through a magnetic stripe reader such that the user of card 400 and others around the user of card 400 may notice that card 400 is visibly illuminated.


Alternately, barcode 416 may be scanned during a transaction. Accordingly, for example, optical sensors 414 may detect light (e.g., laser light) from a barcode scanner that may be scanning barcode 416 and may report the detection to a processor (not shown) of card 400. Based on the detection of the barcode scanner and based on a transaction indication algorithm executed by the processor (not shown) of card 400, a visible indication (e.g., the illumination of LEDs 402) of the transaction may be displayed by card 400.


Persons skilled in the art will appreciate that any type of indication of a transaction may be provided by card 400. For example, in addition to or instead of visible indicators, card 400 may emit sounds via a speaker (not shown) of card 400. As per another example, in addition to or instead of visible indicators, card 400 may emit vibrations via a vibrating device (not shown) of card 400.



FIG. 5 shows card 500. Card 500 may, for example, include a processor (not shown), a battery (not shown), a proximity detector (not shown), an input and/or output device that may exchange information with a point-of-sale terminal, and memory to store a transaction indication algorithm to be executed by the processor. Front side 510 of card 500 may further include design indicia 506 that may be printed or laser etched onto card 500. Devices (e.g., LEDs 502) may be positioned along design indicia 506 such that LEDs 502 may not be visible unless LEDs 502 are illuminated.


Card 500 may, for example, be presented to a point-of-sale terminal (e.g., a magnetic stripe reader, an EMV reader or an RFID reader) associated with a merchant and such presentment may be detected by proximity detectors (not shown) of card 500. Based on the detection of the point-of-sale terminal and based on a transaction indication algorithm executed by the processor of card 500, a visible indication of the transaction may be displayed by card 500. For example, one or more LEDs 502 may be illuminated based on the detection.


Further, card 500 may exchange information with the point-of-sale terminal via a contact-based transfer mechanism, such as an EMV contact mechanism. Alternately, card 500 may exchange information with the point-of-sale terminal via a contactless transfer mechanism, such as an RFID transfer mechanism or an electromagnetic transfer mechanism. Such information may, for example, be indicative of a balance that may be associated with card 500 after card 500 is used for a purchase transaction. Accordingly, for example, a processor (not shown) of card 500 may illuminate a number of LEDs that correspond to a balance of cash remaining on card 500 as may be reported to card 500 by the point-of-sale terminal. For example, four LEDs 502 may be illuminated on front side 510 of card 500 to indicate that approximately 80% of the cash value of card 500 remains after the transaction, such that each LED 502 that is illuminated may represent approximately 20% of the balance remaining on card 500. Alternately, for example, two LEDs 504 may be illuminated on front side 512 of card 500 to indicate that approximately 40% of the cash value of card 500 remains after the transaction.



FIG. 6 shows card 600. Card 600 may, for example, include a processor (not shown), a battery (not shown), a proximity detector (not shown), buttons (not shown) and memory to store an event indication algorithm to be executed by the processor. Card 600 may further include indicia 602 that may be indicative of an issuer of card 600 and indicia 604 that may be indicative of a payment network associated with card 600.


Pressing a button (not shown) of card 600 may, for example, be detected by a processor (not shown) of card 600. Based on the detection, the processor of card 600 may illuminate indicia (e.g., issuer indicia 602) in some manner. For example, only the first letter of issuer indicia 602 may be illuminated. As per another example, each letter of issuer indicia 602 may be separately illuminated in sequence upon detection of a button press. As per yet another example, each letter of issuer indicia 602 may be lit simultaneously, but the color and/or intensity of each letter may be different and/or may be varied.


Card 600 may, for example, be swiped through a magnetic stripe reader located at a point-of-sale terminal and such a swipe may be detected by proximity detectors (not shown) of card 600. Based on the detection of the magnetic stripe reader and based on an event indication algorithm executed by the processor (not shown) of card 600, a visible indication of the transaction may be displayed by card 600. For example, one or more LEDs may be illuminated based on the detection, such that network logo 604 may appear to be glowing with a constant intensity of light, varying intensities of light, a constant duration of light, a varying duration of light, a constant color of light, varying colors of light or any other form of light that may indicate that card 600 has been swiped through a magnetic stripe reader such that the user of card 600 and others around the user of card 600 may notice that card 600 is visibly reacting to a transaction conducted with card 600.


A flow diagram of a detection activity is shown in FIG. 7. Step 711 of sequence 710 may initiate a detection operation, for example, where a property change (e.g., an increased capacitance) associated with a conductive pad is detected. A property change (e.g., a capacitance increase) may then be detected in a second conductive pad (e.g., as in step 712) to verify that a transaction may have occurred when a card (e.g., a payment card) is presented to a point-of-sale terminal (e.g., swiped through a magnetic stripe reader). In step 713, a processor of the card may execute a transaction indicator sequence, whereby the card reacts to the detected transaction by visibly, audibly and/or tactilely reacting to the transaction. For example, personalized features on the card may be caused to illuminate, or glow, based on a detected transaction.


In step 721 of sequence 720, a property change (e.g., an increased capacitance) associated with a first pad of a set of pads may be detected. A property change (e.g., a capacitance increase) may then be detected in a second pad of the set of pads (e.g., as in step 722), such that a detection of a transaction completed with a card at a point-of-sale terminal may be verified. In step 723, a card may exchange transaction information with the point-of-sale terminal, such that the point-of-sale terminal may communicate transaction details to the card (e.g., the amount of the transaction and the balance left on the card after the transaction amount is deducted from the total amount previously available on the card).


In step 724, a processor of the card may activate a transaction indicator sequence that not only may provide a visible, audible and/or a tactile reaction to the transaction, but that may also provide indicia that pertains to certain details of the transaction. For example, a number of LEDs on the card may be illuminated, where the number of LEDs illuminated may correspond to a balance left on a payment card after the payment card is used for a purchase transaction. As per another example, a number of letters associated with issuer indicia on the card may be caused to illuminate, or glow, where the number of letters illuminated may be indicative of a balance left on a payment card after the payment card is used for a purchase transaction. As per yet another example, an expiration date on the card may be caused to illuminate, or glow, if the expiration date is close (e.g., the card is within one month of expiration). Another example may include providing visible indicia (e.g., causing a network logo on the card to glow) if the user of the card has just been awarded a gift (e.g., an instant cash award) by the merchant as may be reported to the card by the merchant's point-of-sale terminal.


Super Smart Secure Payment Applets With Pre-Stored Messages and Logic and Ability To Change Subsequent Function Thereon


A payment card or other device such as a powered card, payment phone and/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. Issuer scripts may be used by the issuer and/or a remote server to update and change parameters and values on a secure element as part of a transaction communication.


The transaction may be a 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 multiple-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.


During a transaction, a payment device may request information. 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).


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.


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.


For example, a card may include a display, for example, 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). Persons skilled in the art will appreciate that 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. Accordingly, 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., 9 am 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.


Messages may be displayed on the payment device for example based on the first authorized transaction after a certain date/time. For example, a message may be pre-stored and displayed on the first authorized transaction after the first year of being issued the payment device or payment account on the payment device.


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, programmable contactless chips, cellular chips and antennas for downloading data from a remote source, manual interfaces, sound interfaces, and/or the like.


Security features may be provided based on the received data. For example, 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 and/or according to an issuer script. For example, 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. After each authorized transaction, for example, 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.


Cards or other devices may utilize an array of LEDs to be used to display and/or convey information to a user (e.g., cardholder). The LED arrays may be under the control of, for example, a general purpose microcontroller on the card. The cards or other devices may include dynamic magnetic communications devices and/or static magnetic stripes. The LED arrays may be in any configuration deemed necessary to convey information, for example, matrix configurations such as a dot matrix array, may be used to display alphanumeric messages (e.g., static or scrolling), and/or may be used to display images (e.g., static or moving) (FIG. 8).


The LED arrays may be in a random or ordered array configuration to display a sequence or imagery, for example, a fireworks display (FIG. 9). Random Images may be lit statically or in sequence (FIG. 10).


According to example embodiments, power on configurations may include card configurations with buttons to turn on the card and/or button-less card configurations that turn on when inserted into a RFID or EMV Reader. A button-less configuration may be applied whether or not the card or other device includes buttons.


Intelligence to decide messages may include PDOL/CDOL information utilized to determine a message. Items available from the terminal may be as follows:


Amount, Authorized (Numeric)


Amount, Other (Numeric)


Terminal Country Code


Terminal Verification Results


Transaction Currency Code


Transaction Data


Transaction Type


Data Authentication Code


ICC Dynamic Number


CVM Results


Transaction Time


Merchant Custom Data


Transaction Currency Code


Transaction Date


Transaction Type


TVR


Unpredictable Number


PDOL/CDOL information may be used to display messages such as Happy Birthday based on, for example, a date (e.g., Transaction Date). Additional Rewards may be based on a transaction amount (e.g., Amount, Authorized). The information may be displayed in a variety of ways, for example, as a message on a dot matrix display and/or the “fireworks going off” (FIG. 9) indicating that the cardholder is a “winner” which may be known to the user as a criteria when the card or other device is received.


Issuer Scripts may be used by a financial institution (e.g., a bank) to send information to the card or other device during a transaction.


The issuer can inform the user of things, for example:


Additional rewards (e.g., based on total spend).


Reduced interest rate (e.g., based on level of usage).


Change in payment product Tier.


This information may be displayed as a message on a dot matrix display and/or the “fireworks going off” indicating that they are a “winner” which would be known by the user as a criteria when the card was received.


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. Persons skilled in the art will appreciate that 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:


Amount, Authorized (Numeric)


Amount, Other (Numeric)


Terminal Country Code


Terminal Verification Results


Transaction Currency Code


Transaction Data


Transaction Type


Data Authenticiation Code


ICC Dynamic Number


CVM Results


Transaction Time


Merchant Custom Data


Transaction Currency Code


Transaction Date


Transaction Type


TVR


Unpredictable Number


According to example embodiments, methods of personalization and personalization updates to credit cards in the field are disclosed.


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 200, or any number of LEDs.


Perso Data Encryption. According to some example embodiments, encrypted personalization data may be sent over a transmission link (e.g., cell network, Bluetooth, NFC, etc.). A personalization data block may have a unique session identifier preprogrammed into a secure element (SE) which may be used as part of an decryption process.


Data may be encrypted at multiple levels. For example, a two level embodiment may include transmission link encryption. An entire block of personalization 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 personalization data (personal data of a cardholder)—sensitive personalization 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 personalization data block that was received. The GP may provide the unique session identifier provided with the personalization 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 personalization 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 personalization data. The unique session identifier may be provided to the SE to be able identify the proper preloaded keys to decrypt the sensitive personalization data. Multiple unique sensitive personalization data keys (each associated with a unique Session Identifier) may be preloaded such that multiple personalization 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. According to some example embodiments, preloading either multiple entire sets of personalization data or multiple partial sets of personalization 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.


Complete sets of Perso Data—Multiple sets of Perso Data which may include changes based on an update to PAN sequence number only or entirely different PANs can be preloaded on the SE. Each of the accounts 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.


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.


Metal and Pseudo Metal Cards


According to example embodiments, a metal may be coated on a non-metal surface, for example, a plastic and/or glass (e.g., flexible glass) skin layer. For example, metal may be poured, sprayed, extruded and/or applied by mold processing. According to some example embodiments, 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. Metal may be deposited by, for example, evaporation, sputter coating, and/or thermal heat transfer.


The deposition may be conformal and/or result in a planar surface. For example, 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.


Metal coating may be excluded in sensitive areas that include, for example, EMV contacts, LED lights, and electronic screens, using a mask. According to some example embodiments, a mask may be provided, for example, by using resist based processes and/or stickers. For example a sticker may be applied to a layer on which metal will be deposited and removed after the deposition. Metal patterning may be performed by, for example, shadow mask (contact and non-contact), tape off, laser removal and photoresist lift off.


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.


After metal coating, the metal may be covered with a protective and/or visual enhancement layer or layers. A protective film may be applied via, for example, printing, thermal transfer and/or spray coating.


Several surface materials may be used. For example, PolyCarb, PolyEster, Kapton tape and/or glass.


A protective film visual enhancement layer or layers may include, for example, printed textures and light bending patterns.


Persons skilled in the art will appreciate that the present invention is not limited to only the embodiments described. Instead, the present invention more generally involves dynamic information and the exchange thereof. Persons skilled in the art will also appreciate that the apparatus of the present invention may be implemented in other ways than those described herein. All such modifications are within the scope of the present invention, which is limited only by the claims that follow.

Claims
  • 1. A method, comprising: receiving, by a payment device, data from a reader;analyzing the data to determine an event trigger associated with an event is present in the data; andproviding a visual display associated with the event based on the event trigger.
  • 2. A method, comprising: receiving, by a payment device, an issuer script from a reader, the issuer script including an event trigger associated with an event; andproviding, on the payment device, a visual display associated with the event.
  • 3. A method, comprising: receiving, by a payment device, an issuer script from a reader, the issuer script including instructions; andproviding a visual display on the payment device based on the instructions.
  • 4. The method of claim 1, wherein the data includes a processing options data objects list (PDOL).
  • 5. The method of claim 1, wherein the data includes a card risk management data objects list (CDOL).
CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional Patent Application Nos. 62/911,357, titled “ADVANCED SECURE PAYMENT DEVICE,” filed Oct. 6, 2019 (Attorney Docket No. D/177PROV), 62/927,664, titled “SCALABLE LOYALTY PROCESSING APPARATUSES AND SYSTEMS AND METHODS OF HIGH VOLUME LOYALTY DATA PROCESSING,” filed Oct. 29, 2019 (Attorney Docket No. D/178PROV), 62/934,343, titled “SWITCH CARD OR DEVICE AND SYSTEM WITH MULTIPLE SECURE ELEMENTS,” filed Nov. 12, 2019 (Attorney Docket No. D/179PROV), 62/967,539, titled “SYSTEMS AND METHODS FOR TRANSACTION DETECTION AND TRANSACTION INDICATOR MECHANISMS FOR CARDS AND DEVICES,” filed Jan. 29, 2020 (Attorney Docket No. D/180PROV), and 62/987,276, titled “MULTI-FUNCTION APPLET POWERED CARDS AND OTHER DEVICES,” filed Mar. 9, 2020 (Attorney Docket No. D/181PROV), 62/987,279, titled “MULTI-FUNCTION APPLET POWERED CARDS AND OTHER DEVICES,” filed Mar. 9, 2020 (Attorney Docket No. D/181PROV), and 63/048,073, titled “PAYMENT DEVICE APPLETS WITH PRE-STORED MESSAGES AND TRIGGERABLE LOGIC,” filed Jul. 3, 2020 (Attorney Docket No. D/190PROV), each of which is hereby incorporated by reference herein in its entirety.

Provisional Applications (7)
Number Date Country
62911357 Oct 2019 US
62927664 Oct 2019 US
62934343 Nov 2019 US
62967539 Jan 2020 US
62987276 Mar 2020 US
62987279 Mar 2020 US
63048073 Jul 2020 US