IP Library › Granted Patent US 12,737,748
Granted Patent B2
US 12,737,748 · App. 18/796,235 · Granted Sep 15, 2026

Multi-function electronic payment card and device system

Inventor: David Wyatt (Austin, TX)
Assignee: Cardware, Inc.
G06Q20/341G06K19/06206G06K19/0716G06K19/07749G06Q20/06G06Q20/065G06Q20/223G06Q20/24G06Q20/346G06Q20/347G06Q20/352G06Q20/3827G06Q20/385G06Q20/4012G06Q20/409G07F7/0873G07F19/00
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,737,748
App. No.
18/796,235
Granted
Sep 15, 2026
Kind
B2
Abstract

A payment card device includes a thin card-shaped payment-card-standard compatible body, a memory, a processor coupled to the memory; and a payment card reader interface. The payment card reader interface includes at least one interface selected from a set of payment-card-standard interfaces consisting of: a smart card reader interface, a magnetic-stripe interface, an RF interface, an NFC interface, a display interface, an information visible on the surface of the payment card device, and a wireless interface. The payment information for a transaction is operable to be conveyed via at least one of the payment-card-standard interfaces, and includes a limited-use payment information. The limited-use payment information is limited to a use only on the selected payment card interface used at a payment card reader facility. The limited-use payment information is invalid in a use other than via the selected payment card interface.

Claims (147)

1 . A payment device comprising:

a thin card-shaped body having a security feature associated with a viewable surface of said thin card-shaped body;

a memory;

a processor coupled to the memory;

an information of an authorized user, an issuer account, and of an issuer, of said payment device;

a payment interface, including at least one interface selected from a set consisting of: a magnetic stripe interface, a smart card interface, an RF interface, an NFC interface, a display interface, and a wireless interface, and

wherein the payment interface is operable to generate a payment information of a payment transaction and said payment information comprises limited-use payment information, and

wherein further, the limited-use payment information is to be used for payment transactions by an authorized user of said payment device at supported payment facilities,

wherein at least a portion of said limited-use payment information is provided by a payment authority for use by the payment device, and

wherein the payment authority rejects as invalid any use of said limited-use payment information obtained at any payment facility other than a payment facility receiving said limited-use payment information via the payment interface.

2 . The device of claim 1 wherein the security feature associated with the viewable surface of the thin card-shaped body comprises no payment numbers susceptible to a misuse by theft, fixed thereon, and

wherein further generation of the limited-use payment information, including that generated by an authorized device connected to the payment device, obviates any need for said payment numbers fixed on said viewable surface.

3 . The device of claim 2 , wherein the viewable surface comprises fixed information disposed thereon and wherein the fixed information includes: a card-holder name; a payment issuing logo; and a card payment network logo, and

wherein further, the viewable surface is free of account numbers, expiration dates, card security codes, or other payment-usable numbers, susceptible to a misuse by theft.

4 . The device of claim 2 , wherein the payment information conveyed via the magnetic stripe interface is limited to the magnetic stripe interface for the issuer account,

wherein further the limited-use payment information is limited to use by the payment device and is operable for conveying payment information to a magnetic-stripe payment card reader,

wherein said limited-use payment information has a limited period of valid use, and

wherein said limited-use payment information is not valid when used other than at a magnetic stripe payment card reader facility.

5 . The device of claim 1 , wherein an information unique to said payment device and to an authorized user thereof, is operable to be conveyed to a personal computing device, for generation of an additional limited-use payment information on said personal computing device, and

wherein further, the additional limited-use payment information is operable to be used for performing payment transactions at payment facilities with which the payment device is limited in performing.

6 . The device of claim 5 , wherein a request for payment includes at least one of a set consisting of: payment information, transactional information, merchant information, payment facility information, payment interface information, and payment card reader information, and

wherein a card-present transaction is one performed by said authorized user presenting said payment device at a payment reader facility for payment, and

wherein a card-not-present transaction is one performed other than when said payment card device is presented for payment at a payment card reader facility; and,

wherein a payment processing facility is operable to approve as valid, a use of the limited-use payment information in a card-present payment transaction at supported facilities; and,

wherein said payment processing facility is also operable to reject, as invalid, a use of the limited-use payment information in a card-not-present payment transaction; and

wherein a payment authority receiving a validation said payment processing facility is operable to decline a payment transaction not approved as valid, and approve a payment transaction as valid, dependent-on said validation of said payment processing facility of said payment transaction.

7 . The device of claim 6 , wherein the payment processing facility shares at least a portion of a same information used in the limited-use payment information and in the additional limited-use payment information, and

wherein further, said payment processing facility is operable to receive said payment information from said payment transaction and to approve or not approve, said payment transaction performed within a valid set of limitations in usage, and

wherein further, said payment processing facility limits valid approval based on payment information matching an expected device generated limited-use payment information, and

wherein said payment processing facility declines as invalid a use of said limited-use payment information in payment transactions other than supported facility payment transactions, and

wherein the personal computing device is configured to receive an authorized user input approving or not approving, the payment transaction, via a user interface disposed of said personal computing device, and

wherein the personal computing device is configured to transmit to the payment processing facility, an approval or a denial via a wireless interface disposed of said personal computing device, and

wherein the payment processing facility limits as validated use for payment for payment transactions with the authorized user approving, and declines as invalid use when the authorized user is denying an approval.

8 . The device of claim 7 , wherein said limited-use payment information comprises a dynamically-generated one-time limited-use payment information portion generated by a processor of siad personal computing device when used at a payment facility accessible to said personal computing device, and

wherein the payment information conveyed to a payment facility, at a payment transaction time, includes at least one of a portion of: a static limited-use portion; and a dynamically-generated limited-use portion, and

wherein at least a portion of said static limited-use portion is provided by the payment authority or a payment processing facility approved by the payment authority, for use by the personal computing device, and

wherein a dynamically generated limited-use payment information includes at least one specific information selected from a set consisting of: a payment device specific information, a personal computing device specific information, a user specific information, a merchant specific information.

9 . The device of claim 5 , wherein a payment processing facility is operable to reject as invalid, a usage of the limited-use payment information, provided by the payment device in card reader facility transactions, when re-used in an online payment transaction, and

wherein said payment processing facility is operable to accept as valid a use of the additional limited-use payment information, when generated via the personal computing device, in a valid online payment transaction use, and

wherein said additional limited-use payment information combines at least one element selected from a set of unique identifying characteristics consisting of: an identifier of the payment device, an identifier of the personal computing device, an authorized user of the personal computing device, an authorized user of the payment device, a specific merchant for the online payment transaction, an identifier of a specific recipient of the online payment transaction, a sequential counter count of transactions, a limited number of payment uses, and an information specific to the online payment transaction.

10 . The device of claim 9 , wherein an interface of said personal computing device is operable to wirelessly receive information of the authorized user of the payment device, and

wherein said issuer of said payment device is operable to support a payment transaction on the personal computing device after receiving an information of the payment device via the personal computing device, and the authorized user of the payment device is verified on the personal computing device through at least one security challenge, selected from a set consisting of:

a device touch ID sensor identifying a recognized touch of a valid user;

a device touch sensor-array receiving a user entered valid user code;

a device key-pad receiving a user entered valid user code;

a device user interface receiving a user entered valid PIN or Key-Code;

a device user interface receiving a correct answer to a challenge presented on the personal computing device which a valid user would know;

a device user interface receiving a user entered valid password;

a device motion-sensing interface reading a user swipe or gesture;

a user tapping a predetermined sequence on the payment device;

a user motioning the payment device in accordance with a sequence;

a skin-contact sensor identifying a recognized valid user;

a device sensor array reading a touch of an identified user;

a device biometric recognition of a valid user; and

a biometric sensing of the payment device remaining continuously in possession of a valid user,

whereupon satisfying said at least one security challenge, an information relating to the payment device is operable to be displayed on the personal computing device through a user interface disposed of the personal computing device, including at least one payment device usage information selected from a set consisting of:

a transaction time;

a payment amount;

a merchant information;

a user information;

an online location;

a payment facility;

a payment device user information;

a payment device issuer information;

at least a numerical portion of the issuer account;

a graphical image representation of at least one of the above set of information;

a graphical image representation of the payment device; and

wherein upon satisfying said at least one security challenge, a user-interface is operable to receive an input, of at least one user action selected from a set comprising: a selection of said payment device in a payment transaction performed by said personal computing device, a selection of a limitation in a limited-use payment, a payment approval authorization; a payment denial; a review of a previous payment transaction, and an adjustment of a payment transaction, and

wherein a display of the personal computing device is operable to convey a status of processing the payment transaction.

11 . A payment device comprising:

a thin card-shaped body having a security feature associated with a viewable surface of said thin card-shaped body;

a memory;

a payment issuer account information;

a processor coupled to the memory;

a payment interface, including at least one supported interface selected from a set of interfaces consisting of: a magnetic stripe interface, a smart card interface, an RF interface, an NFC interface, a display interface, and a wireless interface, and

wherein the payment interface is operable to convey a payment information of a payment transaction, and comprises limited-use payment information,

wherein further an authority in processing of payment transactions is operable to approve as valid a use of the limited-use payment information for payment transactions by an authorized user of said payment device at a limited set of supported payment facilities, and

wherein said authority is operable to reject as invalid, a use of the limited-use payment information provided via the payment interface, in payment transactions not at supported payment facilities.

12 . The device of claim 11 wherein the security feature associated with the viewable surface of the thin card-shaped body comprises no payment numbers susceptible to a misuse by theft, fixed thereon, and

wherein further generating the limited-use payment information, including that generatable by an authorized device connected to the payment device, obviates any need for said payment numbers susceptible to a misuse by theft indicated on said viewable surface.

13 . The device of claim 11 wherein the viewable surface comprises a minimized set of payment information disposed thereon, and wherein the set of payment information includes: a card-holder name; a payment issuing logo; and a card payment network logo, and,

wherein further, the viewable surface is free of payment account numbers, expiration dates, card security codes, or other numbers susceptible to a misuse by theft.

14 . The device of claim 13 , wherein the payment information conveyed via the magnetic stripe interface is specifically limited to the magnetic stripe interface, and

wherein further the limited-use payment information is limited to use specifically by the payment device and is operable for conveying the payment information to a magnetic stripe payment card reader, and

wherein said limited-use payment information has a limited period of valid use, and

wherein said limited-use payment information is not valid when used other than at a magnetic stripe payment card reader facility during the limited period of valid use.

15 . The device of claim 11 , wherein further a payment device information including a unique identifier of said payment device, is operable to be wirelessly conveyed to a personal computing device, for generation of additional limited-use payment information on said personal computing device, and

wherein the personal computing device generated additional limited-use payment information is operable to be used in place of the payment issuer account information for performing payment transactions at payment facilities at which the payment device is limited in performing, and

wherein further a payment issuer approved authority in processing of payment transactions is operable to approve as valid, a use of said personal computing device generated additional limited-use payment information for valid payment transactions by said personal computing device, at payment facilities in addition to those supported by the payment device.

16 . The device of claim 11 , wherein a request for payment includes at least one of a set consisting of: payment information, transaction information, merchant information, payment facility information, payment interface information, and payment card reader information, and

wherein a card-present transaction includes valid payment card reader facility information receiving said payment information via said payment interface; and, wherein a card-not-present transaction is one including at least a portion of said payment information, and not including valid payment card reader facility information; and,

wherein an authority in payment processing is operable to approve or reject a payment transaction, based on an information of the payment transaction, including that of payment facilities involved in the payement transaction; and,

wherein said authority is operable to approve as valid, a valid use of the payment device in a card-present payment transaction; and,

wherein said authority is operable to reject, as not valid, a use or re-use of the limited-use payment information in a card-not-present payment transaction; and

wherein said authority receiving said request for payment is operable to decline a payment transaction not involving a valid card-present use of the limited-use payment information at payment facilities.

17 . The device of claim 11 , wherein a payment issuer approved authority in the processing of payments is operable store at least a portion of the limited-use payment information, for validating a valid use by the payment device; and,

wherein further said authority limits valid approval of said limited-use payment information to perform a card-present payment transaction by the payment device, and wherein said authority declines as invalid a use of said limited-use payment information in payment transactions other than wherein the payment device is present, and

wherein said authority limits said limited-use payment information to use for a finite amount of uses, and declines as invalid use when a count of said of uses has been exceeded, and

wherein said authority limits use to payment for payment transactions when an authorized user approves, and declines as invalid use when the authorized user denies an approval, and

wherein said authority limits said limited-use payment information to a valid use for payments by the payment device.

18 . The device of claim 11 , wherein an information of the payment device and an authorized user thereof, is operable to be received by a personal computing device, via an interface of said personal computing device, and

wherein said personal computing device is operable to identify a valid user for performing payment transactions through at least one user-validation action, selected from a set consisting of:

a device touch ID sensor identifying a touch of the valid user;

a device touch sensor-array receiving a user entered valid user code;

a device key-pad receiving a user entered valid user code;

a device user interface receiving a user entered valid PIN or Key-Code;

a device user interface receiving a user entered valid password;

a device user interface reading a user swipe or gesture;

a user tapping a predetermined sequence on the payment device;

a user motioning the payment device in accordance with a sequence;

a skin-contact sensing identifying a valid user;

a device sensor array reading a touch of an identified user;

a device biometric recognition of a valid user; and

a biometric sensing of the payment device remaining continuously in possession of a valid user,

wherein a display of the personal computing device is operable to display payment transaction information through a user interface disposed of the personal computing device, including at least one information of a set consisting of:

a transaction time;

a payment amount;

a merchant information;

an user information;

an online location;

a payment facility;

a payment device information;

at least a portion of the payment issuer account information;

an image representational of the payment device; and

wherein upon validating the user, a user-interface is operable to receive a valid user input, of at least one user action selected from a set consisting of: a payment information, a user-desired limitation for a payment transaction, a payment approval authorization; a payment denial; and an adjustment of a payment transaction, and

wherein the personal computing device is operable to convey a status of processing the payment transaction, on the display of the personal computing device.

19 . The device of claim 11 , wherein an additional limited-use payment information comprises a dynamically generated limited-use payment information portion generated by a processor of a personal computing device when used at a payment facility accessible to said personal computing device, and

wherein the payment information conveyed to a payment facility, at a payment transaction time, includes at least one of a portion of: a static limited-use portion; and a dynamically-generated limited-use portion, and

wherein at least a portion of said static limited-use portion is provided by a payment issuer approved authority in the processing of payments for use in place of the payment device by a valid user of the personal computing device, and

wherein said dynamically-generated limited-use payment information portion combines at least one specific information selected from a set consisting of: a payment device specific information, a personal computing device specific information, an information supplied by an issuer of payment device, a user specific information, a merchant specific information.

20 . A payment card device comprising:

a thin card-shaped body having a security feature associated with a viewable surface of said thin card-shaped body;

a memory;

a processor coupled to the memory;

a near-field tag; and

a payment facility interface, including at least one supported interface selected from a set of facility interfaces consisting of: a magnetic-stripe, a smart card reader interface, a display interface, an RF interface, an NFC interface, a wireless interface, a visible information fixed thereon said thin card-shaped body, and

wherein an account identifying information for said payment card device is operable to be conveyable to a personal computing device by at least one interface selected from a set consisting of: the set of facility interfaces, and the near-field tag, and

wherein a payment information for a payment transaction is operable to be conveyed via the payment facility interface, for payment transactions by said payment card device at a limited set of supported payment facility types, and

wherein further the payment information is not valid for performing payment transactions not at supported payment facility types,

wherein at least a portion of said payment information comprises limited-use numbers which are limited to valid use at supported payment facility types, and

wherein said limited-use numbers are shared with a payment processing facility for recognition by said payment processing facility of valid usage within limitations upon a generation by the payment card device and a generation by said personal computing device, and

wherein the payment processing facility rejects as invalid any use of said limited-use numbers obtained at any payment facility other than a payment facility receiving generated limited-use numbers at an expected payment facility.

21 . The payment card device of claim 20 , wherein the security feature associated with the viewable surface of the thin card-shaped body comprises no payment numbers susceptible to a misuse by theft, fixed thereon, and

wherein further generation of the limited-use numbers obviates any need for said payment numbers susceptible to a misuse by theft fixed on said viewable surface.

22 . The payment card device of claim 21 , wherein a payment processing facility is operable to reject as invalid, an invalid re-use of limited-use numbers provided via a payment reader facility, in an online payment transaction.

23 . The payment card device of claim 21 , wherein a payment processing facility is operable to reject as invalid, a misuse of limited-use numbers provided via a payment facility other than an expected facility.

24 . The payment card device of claim 21 , wherein a payment processing facility is operable to approve as valid, a use of the limited-use numbers generated via the personal computing device when used at a payment facility accessible to said personal computing device, at payment facilities in addition to payment facility types to which the payment card device is limited.

Continuity (8)
Continuation 17741260 · May 10, 2022
Division 16854829 · Apr 21, 2020
Continuation 16025829 · Jul 2, 2018
Continuation 15250698 · Aug 29, 2016
Continuation 14680946 · Apr 7, 2015
Continuation 14217261 · Mar 17, 2014
Provisional Application 61794891 · Mar 15, 2013
Related Publication 20240394687A1 · Nov 28, 2024
References Cited (308)
US 5528222A · Moskowitz et al. · 1996 [cited by applicant]
US 5594233A · Kenneth et al. · 1997 [cited by applicant]
US 5744787A · Teicher · 1998 [cited by applicant]
US 5883810A · Franklin et al. · 1999 [cited by applicant]
US 5903721A · Sixtus · 1999 [cited by applicant]
US 5963924A · Williams et al. · 1999 [cited by applicant]
US 6005942A · Chan et al. · 1999 [cited by applicant]
US 6076075A · Teicher · 2000 [cited by applicant]
US 6105008A · Davis et al. · 2000 [cited by applicant]
US 6119946A · Teicher · 2000 [cited by applicant]
US 6233683B1 · Chan et al. · 2001 [cited by applicant]
US 6282522B1 · Davis et al. · 2001 [cited by applicant]
US 6330978B1 · Molano et al. · 2001 [cited by applicant]
US 6450407B1 · Freeman et al. · 2002 [cited by applicant]
US 6481632B2 · Wentker et al. · 2002 [cited by applicant]
US 6748367B1 · Lee et al. · 2004 [cited by applicant]
US 6776332B2 · Allen et al. · 2004 [cited by applicant]
US 6938484B2 · Najafi et al. · 2005 [cited by applicant]
US 7004385B1 · Douglass · 2006 [cited by applicant]
US 7127236B2 · Khan et al. · 2006 [cited by applicant]
US 7177848B2 · Hogan et al. · 2007 [cited by applicant]
US 7258012B2 · Xie · 2007 [cited by applicant]
US 7280096B2 · Marvit · 2007 [cited by applicant]
US 7580898B2 · Brown et al. · 2009 [cited by applicant]
US 7593000B1 · Chin · 2009 [cited by applicant]
US 7725369B2 · Shiftan et al. · 2010 [cited by applicant]
US 7740168B2 · Hammad et al. · 2010 [cited by applicant]
US 7793851B2 · Mullen · 2010 [cited by applicant]
US 7907838B2 · Nasiri · 2011 [cited by applicant]
US 7908216B1 · Davis et al. · 2011 [cited by applicant]
US 8052052B1 · Power · 2011 [cited by applicant]
US 8095113B2 · Kean et al. · 2012 [cited by applicant]
US 8103588B2 · Patterson · 2012 [cited by applicant]
US 8127999B2 · Diamond · 2012 [cited by applicant]
US 8255323B1 · Casey et al. · 2012 [cited by applicant]
US 8341557B2 · Pisula et al. · 2012 [cited by applicant]
US 8351910B2 · Horodezky et al. · 2013 [cited by applicant]
US 8423462B1 · Amacker et al. · 2013 [cited by applicant]
US 8646059B1 · von Behren et al. · 2014 [cited by applicant]
US 8892390B2 · MacGougan et al. · 2014 [cited by applicant]
US 8909138B2 · Rhelimi · 2014 [cited by applicant]
US 8930274B1 · Brickell et al. · 2015 [cited by applicant]
US 8952832B2 · Nasiri et al. · 2015 [cited by applicant]
US 9008616B2 · Wall et al. · 2015 [cited by applicant]
US 9256871B2 · Anderson et al. · 2016 [cited by applicant]
US 9600808B1 · Gomez, Sr. et al. · 2017 [cited by applicant]
US 9619741B1 · Rigatti · 2017 [cited by applicant]
US 9619799B2 · Haggerty et al. · 2017 [cited by applicant]
US 9721319B2 · Smets et al. · 2017 [cited by applicant]
US 9898728B2 · Brudnicki et al. · 2018 [cited by applicant]
US 10121144B2 · Khan · 2018 [cited by applicant]
US 10181121B2 · Roberts et al. · 2019 [cited by applicant]
US 10380573B2 · Lin et al. · 2019 [cited by applicant]
US 10445723B2 · Laracey · 2019 [cited by applicant]
US 10510056B2 · Carter et al. · 2019 [cited by applicant]
US 10628820B2 · Wyatt · 2020 [cited by applicant]
US 10861090B2 · Haggerty et al. · 2020 [cited by applicant]
US 11042846B2 · Dicker et al. · 2021 [cited by applicant]
US 11068875B2 · Khan et al. · 2021 [cited by applicant]
US 11176538B2 · Wyatt · 2021 [cited by applicant]
US 11328286B2 · Wyatt · 2022 [cited by applicant]
US 11392937B2 · Dicker et al. · 2022 [cited by applicant]
US 11620634B2 · Wyatt · 2023 [cited by applicant]
US 20020174075A1 · Mirlas et al. · 2002 [cited by applicant]
US 20030222152A1 · Boley, Jr. · 2003 [cited by applicant]
US 20040127256A1 · Goldthwaite et al. · 2004 [cited by applicant]
US 20050043997A1 · Sahota et al. · 2005 [cited by applicant]
US 20050252961A1 · Rasti · 2005 [cited by applicant]
US 20060097991A1 · Hotelling et al. · 2006 [cited by applicant]
US 20060122931A1 · Walker et al. · 2006 [cited by applicant]
US 20060186195A1 · Gray · 2006 [cited by applicant]
US 20070045403A1 · Slonecker, Jr. · 2007 [cited by applicant]
US 20070055630A1 · Gauthier et al. · 2007 [cited by applicant]
US 20070076923A1 · Chiu · 2007 [cited by applicant]
US 20070095892A1 · Lyons et al. · 2007 [cited by applicant]
US 20070114274A1 · Gibbs et al. · 2007 [cited by applicant]
US 20070208671A1 · Brown et al. · 2007 [cited by applicant]
US 20070244811A1 · Tumminaro · 2007 [cited by applicant]
US 20070265984A1 · Santhana · 2007 [cited by applicant]
US 20070278291A1 · Rans et al. · 2007 [cited by applicant]
US 20080017704A1 · VanDeburg et al. · 2008 [cited by applicant]
US 20080040285A1 · Wankmueller · 2008 [cited by applicant]
US 20080078831A1 · Johnson et al. · 2008 [cited by applicant]
US 20080110983A1 · Ashfield · 2008 [cited by applicant]
US 20080122796A1 · Jobs et al. · 2008 [cited by applicant]
US 20080172317A1 · Deibert et al. · 2008 [cited by applicant]
US 20080222047A1 · Boalt · 2008 [cited by applicant]
US 20080275779A1 · Lakshminarayanan · 2008 [cited by applicant]
US 20080319905A1 · Carlson · 2008 [cited by applicant]
US 20090030845A1 · Hurry et al. · 2009 [cited by applicant]
US 20090070272A1 · Jain · 2009 [cited by applicant]
US 20090083850A1 · Fadell et al. · 2009 [cited by applicant]
US 20090144161A1 · Fisher · 2009 [cited by applicant]
US 20090159700A1 · Mullen · 2009 [cited by examiner]
US 20090200371A1 · Kean et al. · 2009 [cited by applicant]
US 20090210308A1 · Toomer et al. · 2009 [cited by applicant]
US 20090276347A1 · Kargman · 2009 [cited by applicant]
US 20090291634A1 · Saarisalo · 2009 [cited by applicant]
US 20090307132A1 · Phillips · 2009 [cited by applicant]
US 20090320123A1 · Yu et al. · 2009 [cited by applicant]
US 20100078471A1 · Lin et al. · 2010 [cited by applicant]
US 20100078472A1 · Lin et al. · 2010 [cited by applicant]
US 20100082445A1 · Hodge et al. · 2010 [cited by applicant]
US 20100082481A1 · Lin et al. · 2010 [cited by applicant]
US 20100082490A1 · Rosenblatt et al. · 2010 [cited by applicant]
US 20100088227A1 · Belamant · 2010 [cited by applicant]
US 20100125508A1 · Smith · 2010 [cited by applicant]
US 20100125509A1 · Kranzley et al. · 2010 [cited by applicant]
US 20100127083A1 · Brown et al. · 2010 [cited by applicant]
US 20100185545A1 · Royyuru et al. · 2010 [cited by applicant]
US 20100217709A1 · Aabye et al. · 2010 [cited by applicant]
US 20110010277A1 · Enzaldo · 2011 [cited by applicant]
US 20110022472A1 · Zon · 2011 [cited by applicant]
US 20110070826A1 · Griffin et al. · 2011 [cited by applicant]
US 20110078031A1 · Mardikar et al. · 2011 [cited by applicant]
US 20110082772A1 · Hirson · 2011 [cited by applicant]
US 20110101093A1 · Ehrensvärd · 2011 [cited by applicant]
US 20110112918A1 · Mestré et al. · 2011 [cited by applicant]
US 20110140841A1 · Bona et al. · 2011 [cited by applicant]
US 20110153498A1 · Makhotin et al. · 2011 [cited by applicant]
US 20110173060A1 · Gallagher · 2011 [cited by applicant]
US 20110173121A1 · Kawan · 2011 [cited by applicant]
US 20110184867A1 · Varadarajan · 2011 [cited by applicant]
US 20110191161A1 · Dai · 2011 [cited by applicant]
US 20110191177A1 · Blackhurst et al. · 2011 [cited by applicant]
US 20110238573A1 · Varadarajan · 2011 [cited by applicant]
US 20110282785A1 · Chin · 2011 [cited by applicant]
US 20120011058A1 · Pitroda et al. · 2012 [cited by applicant]
US 20120116902A1 · Cardina et al. · 2012 [cited by applicant]
US 20120116976A1 · Cardina et al. · 2012 [cited by applicant]
US 20120123937A1 · Spodak · 2012 [cited by applicant]
US 20120143754A1 · Patel · 2012 [cited by applicant]
US 20120148115A1 · Birdwell et al. · 2012 [cited by applicant]
US 20120150687A1 · Hart · 2012 [cited by applicant]
US 20120150750A1 · Law · 2012 [cited by applicant]
US 20120169593A1 · Mak et al. · 2012 [cited by applicant]
US 20120191612A1 · Spodak et al. · 2012 [cited by applicant]
US 20120191615A1 · Shibuk · 2012 [cited by applicant]
US 20120197691A1 · Grigg et al. · 2012 [cited by applicant]
US 20120205443A1 · Routhenstein et al. · 2012 [cited by applicant]
US 20120206406A1 · Kim et al. · 2012 [cited by applicant]
US 20120290449A1 · Mullen et al. · 2012 [cited by applicant]
US 20120310760A1 · Phillips et al. · 2012 [cited by applicant]
US 20130013499A1 · Kalgi · 2013 [cited by applicant]
US 20130024371A1 · Harraman et al. · 2013 [cited by applicant]
US 20130036050A1 · Gordano et al. · 2013 [cited by applicant]
US 20130054474A1 · Yeager · 2013 [cited by applicant]
US 20130068366A1 · Eng · 2013 [cited by applicant]
US 20130087627A1 · Marseille et al. · 2013 [cited by applicant]
US 20130097040A1 · Fisher · 2013 [cited by applicant]
US 20130151292A1 · Van Deloo et al. · 2013 [cited by applicant]
US 20130159186A1 · Brudnicki et al. · 2013 [cited by applicant]
US 20130166441A1 · Kobylkin et al. · 2013 [cited by applicant]
US 20130232083A1 · Smith et al. · 2013 [cited by applicant]
US 20130262317A1 · Collinge et al. · 2013 [cited by applicant]
US 20130297509A1 · Sebastian et al. · 2013 [cited by applicant]
US 20140006276A1 · Grigg et al. · 2014 [cited by applicant]
US 20140019367A1 · Khan et al. · 2014 [cited by applicant]
US 20140229375A1 · Zaytzsev et al. · 2014 [cited by applicant]
US 20140310113A1 · Sengupta et al. · 2014 [cited by applicant]
US 20140344153A1 · Raj et al. · 2014 [cited by applicant]
US 20150058191A1 · Khan et al. · 2015 [cited by applicant]
US 20150073983A1 · Bartenstein et al. · 2015 [cited by applicant]
US 20150134540A1 · Law et al. · 2015 [cited by applicant]
US 20150178724A1 · Ngo et al. · 2015 [cited by applicant]
US 20150180836A1 · Wong et al. · 2015 [cited by applicant]
US 20150348002A1 · Van Os et al. · 2015 [cited by applicant]
US 20160042356A1 · Jakobson et al. · 2016 [cited by applicant]
US 20160057619A1 · Lopez · 2016 [cited by applicant]
US 20160253669A1 · Yoon et al. · 2016 [cited by applicant]
US 20160275505A1 · Salian et al. · 2016 [cited by applicant]
US 20160321653A1 · Jacobs et al. · 2016 [cited by applicant]
AU 2013209318 · 2014 [cited by applicant]
EP 0949595 · 1999 [cited by applicant]
EP 1004992 · 2000 [cited by applicant]
EP 1223565 · 2002 [cited by applicant]
EP 2302882 · 2011 [cited by applicant]
EP 2407919 · 2012 [cited by applicant]
JP 200413728 · 2004 [cited by applicant]
KR 20110039946 · 2011 [cited by applicant]
KR 20120076502 · 2012 [cited by applicant]
WO 9417498 · 1994 [cited by applicant]
WO 2009082760 · 2009 [cited by applicant]
WO 2010037218A1 · 2010 [cited by applicant]
WO 2010039337 · 2010 [cited by applicant]
WO 2012011054 · 2012 [cited by applicant]
WO 2012042262 · 2012 [cited by applicant]
WO 2012042262A1 · 2012 [cited by applicant]
WO 2012154915 · 2012 [cited by applicant]
WO 2013155627 · 2013 [cited by applicant]
U.S. Appl. No. 14/395,457, filed Dec. 5, 2023, Law et al. [cited by applicant]
Visa Token Service—Product Fact Sheet 2022 Visa; 2 pages. [cited by applicant]
Visa Token Service—Visa 2025; 7 pages. [cited by applicant]
Visa Token Service Momentum, Annual Update 2022; Visa; 2 pages. [cited by applicant]
What is Venmo, how does it work, and is it safe to use? May 31, 2024 Ben Luthi Yahoo Finance; 6 pages. [cited by applicant]
What is Venmo: How it Works May 18, 2023; Nicole Symon; 9 pages. [cited by applicant]
What is Venmo?—NerdWallet Jun. 24, 2024; Chanelle Bessette; 7 pages. [cited by applicant]
Google Wallet and the New Retail Ecosystem Oct. 3, 2011 David W. Schropfer; 3 pages. [cited by applicant]
Government Smart Card Handbook Feb. 2004 GSA; 262 pages.(Uploaded as Prt1 and Prt2). [cited by applicant]
Implementing Electronic Card Payment Systems 2003 Cristian Radu; 49 pages. [cited by applicant]
Java Card for ePayment Applications 2002 Vesna. Hassler; 40 pages. [cited by applicant]
Java Card Platform: A Week in the Life of Jack Link 2004 Sun Microsystems; 6 pages. [cited by applicant]
Java Card Questions and Answers with Zhiqun Chen Oct. 2000 Ed Ort Sun Microsystems; 4 pages. [cited by applicant]
Java Card Technology Datasheet 2005 Sun Microsystems; 3 pages. [cited by applicant]
Java Card Technology Examples 2004 Sun Microsystems. [cited by applicant]
Java Card Technology FAQs 2005 Sun Microsystems; 3 pages. [cited by applicant]
Venmo; Just say “Venmo Me”; 2021; 24 pages. [cited by applicant]
Java Card Technology for Smart Cards: Architecture and Programmer's Guide Book information Zhiqun Chen Sun Microsystems; 36 pages. Year 2000; date unkown. [cited by applicant]
Java Card1_Fig-12 2006 Sun.com; 1 page. [cited by applicant]
Java Card1_Fig-3 2005 Sun.com; 1 page. [cited by applicant]
Java Card1_Fig-4 2005 Sun.com; 1 page. [cited by applicant]
Java Card1_Fig-5 2006 Sun.com; 1 page. [cited by applicant]
Java Card1_Fig-7 2004 Sun.com; 1 page. [cited by applicant]
Java Card1_Fig-9 2004 Sun.com; 1 page. [cited by applicant]
Java on Smart Cards: Programming and Security: First International Workshop, JavaCard 2000; Isabelle Attali, Jefferson Jensen; 25 pages. [cited by applicant]
JavaCard—From Hype to Reality 1999 Michael Baentsch; IEEE; 8 pages. [cited by applicant]
JavaCard—Redistribution and Use in Source and Binary Forms License 2004 Sun Microsystems; 5 pages. [cited by applicant]
JCOP V2.4.1 Secure Smart Card Controller, Rev. 3.2 Sep. 2, 2009;NXP; 18 pages. [cited by applicant]
JCOP20 Technical Brief, Revision 2.3; IBM; 9 pages; Feb. 2002. [cited by applicant]
JCOP30 Technical Brief, Revision 2.3; 9 pages; Feb. 2002. [cited by applicant]
MagTek CEO: “Dynamic Data is the Core of Security” [Transcript] Mar. 8, 2012 David Evans; Payments; 11 pages. [cited by applicant]
MagTek Introduces Qwick Code Mobile Wallet Jan. 15, 2012; 1 page. [cited by applicant]
MagTek Launches QwickPAY, the Innovative Secure Mobile Payments Service, Into the Android Marketplace Mar. 29, 2011 Magtek; 1 page. [cited by applicant]
Visa Invests in Authentication Outfit Emue Nov. 18, 2009 Finextra; 2 pages. [cited by applicant]
Visa CodeSure Gets Commercial Green Light; Jun. 2, 2010; Finextra; 3 pages. [cited by applicant]
Mastercard Virtual Card Tokens; Mar. 7, 2025; Mastercard; 1 page. [cited by applicant]
MDES Token Connect | Mastercard Developers; Mastercard; 1 page; Apr. 2, 2025. [cited by applicant]
Mobile Payment Services in South Africa; Jan. 31, 2013; Matthias Beland; 124 pages. [cited by applicant]
NXP—News Center—Infocus Archive 2006 NXP; 4 pages; Oct. 22, 2024. [cited by applicant]
One-Click Payments by 2030 With Tokenization; Mar. 12, 2025 Jorn Lambert; Mastercard; 4 pages. [cited by applicant]
PCI—Payment Card Industry (PCI) Data Security Standard, Version 2.0 Oct. 2010 PCI; 75 pages. [cited by applicant]
PCI Data Security Standard (PCI DSS), Version 2.0 Aug. 2011 Scoping SIG, Tokenization Taskforce PCI Security Standards Council; 23 pages. [cited by applicant]
PHB Development, Kurt Salmon, “Mobile Payments . . . a “Southern” Revolution!” 2011 PHB Development; 63 pages. [cited by applicant]
Visa Best Practices for Tokenization Version 1.0 Jul. 14, 2010 Visa Best Practices; 4 pages. [cited by applicant]
Qwick Codes Mobile Wallet for IOS CNET; 2005; 11 pages. [cited by applicant]
Visa and Emue Technologies deploy cards with built-in one-time password generator Feb. 9, 2009 Finextra; 1 page. [cited by applicant]
Techie Visa Card Features Buttons and Screen to Generate CCV Dynamically Nov. 11, 2008 Mark Wilson; 1 page. [cited by applicant]
The Complete Guide to Payments Tokenization; 3 pages; Apr. 2, 2025. [cited by applicant]
Venmo, Just Say “Venmo Me” 2021 Venmo; 24 pages. [cited by applicant]
U.S. Appl. No. 61/899,734, filed Nov. 4, 2013; Inventor Ahmer A. Khan; 40 pages. [cited by applicant]
U.S. Appl. No. 61/905,035; Inventor George R. Dicker; et al; Nov. 15, 2013; 58 pages. [cited by applicant]
U.S. Appl. No. 61/921,688, filed Dec. 30, 2013; Inventor Ahmer A. Khan; 54 pages. [cited by applicant]
“A Primer to the Implementation of Smrt Card Management and Related Systems,” Version 1.0 Aug. 2000 GlobalPlatform; 47 pages. [cited by applicant]
“An Introduction to Java Card Technology—Part 1” May 29, 2003 C. Enrique Ortiz Sun Developer Network; 16 pages. [cited by applicant]
“An Introduction to Java Card Technology—Part 2, The Java Card Applet” Sep. 2003 C. Enrique Ortiz Sun Developer Network; 13 pages. [cited by applicant]
“An Introduction to Java Card Technology—Part 3, The Smart Card Host Application” Sep. 2003 C. Enrique Ortiz Sun Developer Network; 11 pages. [cited by applicant]
“An Investigation into Electronic Commerce Frauds and their Security Implications” Nov. 7, 2004 Kevin Boardman; 67 pages. [cited by applicant]
“Contactless Payment Security Questions & Answers” 2016 Smart Card Alliance, Inc.; 4 pages. [cited by applicant]
“EMV Card Personalization Specification,” Version 1.0 Jun. 2003 EMVCo, LLC; 81 pages. [cited by applicant]
“EMV Integrated Circuit Card Specifications for Payment Systems,” Book 1, Application Independent ICC to Terminal Interface Requirements, Version 4.Nov. 3, 2011 EMVCo, LLC; 189 pages. [cited by applicant]
“EMV Integrated Circuit Card Specifications for Payment Systems,” Book 2, Security and Key Management, Version 4.1 May 2004 EMVCo, LLC; 187 pages. [cited by applicant]
“EMV Integrated Circuit Card Specifications for Payment Systems,” Book 2, Security and Key Management, Version 4.3 Nov. 2011 EMVCo, LLC; 174 pages. [cited by applicant]
“EMV Integrated Circuit Card Specifications for Payment Systems,” Book 3, Application Specification, Version 4.1 May 2004 EMVCo, LLC; 237 pages. [cited by applicant]
“EMV Integrated Circuit Card Specifications for Payment Systems,” Book 3, Application Specification, Version 4.. Nov. 2011 EMVCo, LLC; 230 pages. [cited by applicant]
“EMV Integrated Circuit Card Specifications for Payment Systems,” Book 4, Cardholder, Attendant, and Acquirer Interface Requirements, Version 4.3 Nov. 2011 EMVCo, LLC; 154 pages. [cited by applicant]
“Interoperability in Electronic Payments: Lessons and Opportunities” 2012 Carol Coye Benson CGAP; 46 pages. [cited by applicant]
“Investigating Mobile Payment: Supporting Technologies, Methods, and Use” 2005 Valcourt, et al.; IEEE; 8 pages. [cited by applicant]
“Java Card™ 2.2 Off-Card Verifier” White Paper Jun. 2002 Sun Microsystems; 24 pages. [cited by applicant]
“Java Card™ Platform Security” Technical White Paper 2001 Sun Microsystems; 26 pages. [cited by applicant]
“Radio-Frequency Identification (RFID): A Focus on Information Security and Privacy,” OECD Digital Economy Papers, No. 138 Jan. 14, 2008 OECD Publishing; 71 pages. [cited by applicant]
“SE vs. HCE: What is More Secure for NFC Mobile Payments?” Oct. 17, 2014 Finextra; 6 pages. [cited by applicant]
About Us | Venmo 2012 Venmo.com. [cited by applicant]
Apple Press Release: “Apple Announces Apple Pay” Sep. 9, 2014 Apple; 4 pages. [cited by applicant]
GlobalPlatform Technical Overview Jan. 22, 2003 Marc Kekiheff GlobalPlatform; 9 pages. [cited by applicant]
E-ink on Credit Cards will do Away with PINs (video) Sep. 2, 2011 The Digital Reader; 6 pages. [cited by applicant]
Emue—a Revolution in Authentication May 13, 2009 EMUE; 1 page. [cited by applicant]
For Businesses: Payment Technologies—Products & Platforms 2004 Visa; 3 pages. [cited by applicant]
For Businesses: Payment Technologies—Visa Cash 2004 Visa; 1 page. [cited by applicant]
For Businesses: Payment Technologies—Visa Smart debit and Visa Smart Credit 2004 Visa; 2 pages. [cited by applicant]
GlobalPlatform—Implementations—Financial 2006 GlobalPlatform; 7 pages. [cited by applicant]
GlobalPlatform—Implementations—Mobile Telecom 2006 GlobalPlatform; 3 pages. [cited by applicant]
GlobalPlatform—Implementations—Retail 2006 GlobalPlatform; 1 page. [cited by applicant]
GlobalPlatform—Implementations—Transit 2006 GlobalPlatform; 2 pages. [cited by applicant]
GlobalPlatform—Interoperability and Security with GlobalPlatform Feb. 2, 2004 Marc Kekiheff GlobalPlatform; 70 pages. [cited by applicant]
GlobalPlatform—Overview Jun. 2004 GlobalPlatform; 38 pages. [cited by applicant]
GlobalPlatform—The Cross-Industry Approach to Smart Card Standards 2000 GlobalPlatform; 3 pages. [cited by applicant]
GlobalPlatform: a Dynamic and Secure Pre and Post Issuance Solution—Cartes 2002 2002 Marc Kekiheff GlobalPlatform; 28 pages. [cited by applicant]
GlobalPlatform Card Security Requirements Specification Jan. 22, 2003 Marc Kekiheff GlobalPlatform; 13 pages. [cited by applicant]
GlobalPlatform Card Specification Tutorial Jan. 22, 2003 Marc Kekiheff GlobalPlatform; 40 pages. [cited by applicant]
GlobalPlatform Specifications Archive—Technology Document Library 2024 GlobalPlatform; 12 pages. [cited by applicant]
TPM Mobile with Trusted Execution Environment for Comprehensive Mobile Device Security, Jun. 2012; 6 pages. [cited by applicant]
MagTek, Magnetic Stripe Card Standards, (MagTek Inc. eds., 2011); 2 pages. [cited by applicant]
EMVco, LLC, EMV Integrated Circuit Card Specifications for Payment Systems: Book 2—Security and Key Management (EMVCo, LLC eds., Version 4.3 2011); 174 pages. [cited by applicant]
Klaus Finkenzeller, RFID Handbook (John Wiley & Sons, 3rd ed. 2010); 480 pages. [cited by applicant]
Smart Card Alliance, EMV and NFC: Complementary Technologies that Deliver Secure Payments and Value-Added Functionality (Smart Card Alliance, Inc. eds., 2012); 15 pages. [cited by applicant]
Mastercard, MasterCard Approved Mobile Devices, Mastercard (Aug. 3, 2012), http://www.mastercard-mobilepartner.com/docs/MasterCard_Approved_Mobile_Devices.pdf , [ https://web.archive.org/web/20120906234255/http://www.ma… [cited by applicant]
EMVco, LLC, EMV Chip At-a-Glance: Enabling Seamless and Secure Contact and Contactless Payments Around the World, EMVCO (2002), https://www.emvco.com/wp- content/uploads/2022/09/EMV%C2%AE-Chip-At-A-Glance-EMVCo-eBook.pd… [cited by applicant]
Scoping SIG & Tokenization Taskforce PCI Security Standards Council, PCI Data Security Standard (PCI DSS)—Information Supplement: PCI DSS Tokenization Guidelines (PCI Security Standards Council eds., Version 2.0) Year 2… [cited by applicant]
Alessandro Vizzarri et al., Security in Mobile Payments (2013): 6 pages. [cited by applicant]
“The Electronic Purse”, John Wenninger and David Laster, Federal Reserve Bank of New York, 1995 https://www.newyorkfed.org/medialibrary/media/research/current_issues/ci1-1.pdf [https://web.archive.org/web/20170502002450… [cited by applicant]
U.S. Appl. No. 61/619,095 to Collinge et al. [cited by applicant]
U.S. Appl. No. 61/635,248 to Collinge et al. [cited by applicant]
U.S. Appl. No. 61/735,383 to Collinge et al. [cited by applicant]
U.S. Appl. No. 61/762,098 to Collinge et al. [cited by applicant]
Ann Cavoukian, Mobile Near Field Communications (NFC) “Tap 'n Go” Keep it Secure & Private, IPC (2011), https://www.ipc.on.ca/sites/default/files/legacy/Resources/mobile-nfc.pdf; 22 pages. [cited by applicant]
Annika Paus, Near Field Communication in Cell Phones; Jul. 24, 2007; 26 pages. [cited by applicant]
Ashis K. Mahapatra, Touch Screen Systems, Orissa Review (2005), https://magazines.odisha.gov.in/orissareview/jun2005/engpdf/touch_screen_system.pdf; 5 pages. [cited by applicant]
Anup K. Ghosh & Tara M. Swaminatha, Software Security and Privacy Risks in Mobile E-Commerce, 44 CACM 51 (2001); 7 pages/. [cited by applicant]
1747.09 Printing credit or debit card receipts; restrictions, CA Civil, Jan. 2009; 2 pages. [cited by applicant]
Vedat Coskun, Near Field Communication: Theory to Practice (John Wiley & Sons, 1st ed. 2012); 31 pages. [cited by applicant]
The 2013 Federal Reserve Payments Study; Recent and Long-Term Trends in the United States: 2000-2012 Detailed Report and Updated Data Release; Federal Reserve System; Jul. 2014; 191 Pages. [cited by applicant]
The 2013 Federal Reserve Payments Study; Recent and Long-Term Payment Trends in the United States: 2003-2012; Summary Report and Initial Data Release;43 Pages. [cited by applicant]
Over-the-air Deployment of Applications in Multi-Platform Environments; Tore Fjellheim; Queensland University of Technology,2006 Australian Software Engineering Conference;10 Pages. [cited by applicant]
Chapter 12: Hash Functions—The Joy of Cryptography OE (1st); 2017; 23 Pages. [cited by applicant]
This Month in History: The First CreditCard; By Diane Mclaughlin; Banker & Tradesman Staff | Sep. 25, 2022; 2 Pages. [cited by applicant]
Consumer World; Two Months After the Deadline, Most Major Retailers Still Can't Read Chipped Credit Cards; Dec. 7, 2015; 1 page. [cited by applicant]
Tech; Bump Pay Lets you PayPal Someone With a Tap, But Only In-Person; Josh Constine; Mar. 29, 2012; 1 Pages. [cited by applicant]
Colnect; Bank Card: Bank of America; 2003-2025 colnect.com. 4 Pages. [cited by applicant]