Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.

Patents

  1. Advanced Patent Search
Publication numberUS20090271211 A1
Publication typeApplication
Application numberUS 12/431,452
Publication dateOct 29, 2009
Filing dateApr 28, 2009
Priority dateApr 29, 2008
Also published asCA2722933A1, CA2722947A1, CA2722949A1, CA2722951A1, US8770470, US20090266881, US20090271262, US20090271315, WO2009134781A2, WO2009134781A3, WO2009134782A2, WO2009134782A3, WO2009134789A2, WO2009134789A3, WO2009134790A2, WO2009134790A3
Publication number12431452, 431452, US 2009/0271211 A1, US 2009/271211 A1, US 20090271211 A1, US 20090271211A1, US 2009271211 A1, US 2009271211A1, US-A1-20090271211, US-A1-2009271211, US2009/0271211A1, US2009/271211A1, US20090271211 A1, US20090271211A1, US2009271211 A1, US2009271211A1
InventorsAyman Hammad
Original AssigneeAyman Hammad
Export CitationBiBTeX, EndNote, RefMan
External Links: USPTO, USPTO Assignment, Espacenet
Device including user exclusive data tag
US 20090271211 A1
Abstract
A consumer device is disclosed. The device comprises a body, and a memory comprising a computer readable medium disposed on or within the body. The computer readable medium comprises user exclusive data tag, which can be placed in a user exclusive data tag.
Images(7)
Previous page
Next page
Claims(20)
1. A consumer device comprising:
a body; and
a memory comprising a computer readable medium disposed on or within the body, the computer readable medium comprising user exclusive data, wherein the user exclusive data is configured to be transmitted in a user exclusive data tag in an authorization request message.
2. The consumer device of claim 1 further comprising:
a processor coupled to the computer readable medium.
3. The consumer device of claim 1 wherein the consumer device is a phone.
4. The consumer device of claim 1 wherein the consumer device is in the form of a card.
5. A method comprising:
receiving, at a server computer, an authorization request message comprising a user exclusive data tag comprising user exclusive data, wherein the user exclusive data was previously stored in a consumer device;
analyzing the authorization request message; and
performing additional processing based on the user exclusive data.
6. The method of claim 5 further comprising:
wherein performing additional processing comprises initiating the sending of a notification message to the consumer device, and wherein the user exclusive data includes a user's phone number.
7. The method of claim 6 wherein the consumer device is a phone.
8. The method of claim 5 wherein the user exclusive data relates to an instruction to send a receipt to the consumer device.
9. The method of claim 5 wherein the user exclusive data comprises consumer preferences.
10. The method of claim 5 wherein the authorization request message comprises a BIN.
11. A computer useable medium having a computer readable program code embodied therein, said computer readable program code adapted to be executed by a processor, the method comprising:
receiving an authorization request message comprising user exclusive data in a user exclusive data tag;
analyzing the user exclusive data; and
performing additional processing based on the user exclusive data.
12. The computer useable medium of claim 11 wherein the authorization request message further comprises a BIN.
13. The computer useable medium of claim 11 wherein the authorization request message further comprises a form factor indicator tag.
14. A server computer comprising the processor and the computer readable medium of claim 11 coupled to the processor.
15. A system comprising the server computer of claim 14.
16. A method comprising:
obtaining a consumer device comprising a body, and a memory comprising a computer readable medium disposed on or within the body, the computer readable medium comprising user exclusive data; and
using the consumer device to interact with an access device, wherein the access device thereafter generates and sends an authorization request message comprising a user exclusive data tag with the user exclusive data to an issuer associated with the portable consumer device.
17. The method of claim 16 wherein the consumer device is a phone.
18. The method of claim 16 wherein the consumer device is a card.
19. The method of claim 16 wherein the consumer device is a portable consumer device.
20. The method of claim 16 wherein the authorization request message is sent to the issuer via a payment processing network.
Description
    CROSS-REFERENCES TO RELATED APPLICATIONS
  • [0001]
    This application claims priority to and is a non-provisional of U.S. provisional patent application No. 61/048,814, filed on Apr. 29, 2008, which is incorporated herein by reference in its entirety for all purposes.
  • BACKGROUND
  • [0002]
    A traditional payment process utilizing a bank issued payment card includes the reading of data from a contactless payment card in the form of track data. An authorization request message including the data from the contactless payment card is thereafter generated by an access device. This authorization request message is then sent to the issuer of the contactless payment card. Other transaction information including an indicator of the type of transaction (e.g., contactless) and the amount of the transaction is also included in the authorization request message. After the issuer receives the authorization request message, the issuer sends an authorization response message back to the merchant with an immediate authorization or decline of the transaction at the time of the purchase based on the issuer's rules for authorization. This is considered an on-line transaction.
  • [0003]
    While traditional payment processes such as these are useful, improved services and improved functionality in the context of payment transactions would also be desirable.
  • [0004]
    Embodiments of the invention address these and other problems, individually and collectively.
  • BRIEF SUMMARY
  • [0005]
    Embodiments of the invention are directed to consumer devices, methods, and systems that use user exclusive data tags such as customer exclusive data tags in transactions such as purchase transactions.
  • [0006]
    One embodiment of the invention is directed to a consumer device comprising: a body; and a memory comprising a computer readable medium disposed on or within the body, the computer readable medium comprising user exclusive data, wherein the user exclusive data is configured to be transmitted in an authorization request message comprising the user exclusive data in a user exclusive data tag.
  • [0007]
    Another embodiment of the invention is directed to a method comprising: receiving, at a server computer, an authorization request message comprising user exclusive data in a user exclusive data tag, wherein the user exclusive data was previously stored in a consumer device; analyzing the authorization request message; and performing additional processing based on the user exclusive data.
  • [0008]
    Another embodiment of the invention a method comprising: obtaining a consumer device comprising a body, and a memory comprising a computer readable medium disposed on or within the body, the computer readable medium comprising user exclusive data; and using the consumer device to interact with an access device, wherein the access device thereafter generates and sends an authorization request message comprising a user exclusive data tag comprising the user exclusive data to an issuer associated with the portable consumer device.
  • [0009]
    Embodiments of the invention are directed to specific combinations of these different aspects, as well as specific embodiments related to those specific aspects.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • [0010]
    FIG. 1 shows a block diagram of a system that can be used in some embodiments of the invention.
  • [0011]
    FIG. 2( a) shows a block diagram of a consumer device in the form of a phone.
  • [0012]
    FIG. 2( b) shows an illustration of a payment card.
  • [0013]
    FIG. 3 shows a block diagram of an access device according to an embodiment of the invention.
  • [0014]
    FIG. 4 shows a block diagram of a computer apparatus.
  • [0015]
    FIGS. 5-6 show flowcharts illustrating methods performed according to embodiments of the invention.
  • DETAILED DESCRIPTION
  • [0016]
    As technology improves over time, so does the opportunity to include new data to be recognized within a payment processing network, or other suitable network. This new data, which may be alpha and/or numeric, may have various forms depending upon the particular services to be provided. For example, user data may be defined by the issuer of a portable consumer device and may be specific to their own implementation, and/or may be standardized for use by any network node or authorized service provider. The data may be static and personalized onto the portable consumer device prior to issuance. Alternatively or additionally, it may be dynamic and placed into a data tag by a portable consumer device based on point of sale parameters. It may be permanently encoded in a memory in a portable consumer device such as a card, or may be changed by the cardholder after issuance of the card.
  • [0017]
    These services provided after analyzing the data could also be provided by the merchant, payment processing organization, acquirer, or other third party on behalf of the issuer. This data may be provided in the clear and may be directly visible by any of the nodes in the system or may be encrypted and visible by only those that understand the encryption techniques (typically the issuer). Encryption techniques may include symmetric (DES, 3DES) or asymmetric (AES or public key infrastructure—PKI) encryption techniques. Encryption techniques may be global and applied across all portable consumer devices utilizing master keys, or may utilize unique derivation keys for each portable consumer device or groups of portable consumer devices
  • [0018]
    Embodiments of the invention involve the use of a supplementary data field as a vehicle for providing additional data in the authorization request messages from a point of sale to an issuer. The supplementary data field may be Field 55 as defined in Visa Contactless Payment Specification. The supplementary data (i.e., the user specific data) in the supplementary data field can be used for a variety of new services that can enhance traditional transactions.
  • [0019]
    Embodiments of the invention include the use of data tags, assigned or enhanced, to be sent in the supplementary data field, for the purpose of moving additional data in authorization request messages. Exemplary data tags may include a user exclusive data tag and a form factor indicator tag. The user exclusive data tag can be a customer exclusive data tag. The data within these tags may be utilized alone or together, and in the clear or encrypted.
  • [0020]
    A “data tag” may include one or more data elements in any suitable form and typically includes at least a tag identifier element and a value element. In some embodiments, a data tag may include a tag identifier element, a length element, and a value element. The tag identifier element may be embodied by one or more characters, which indicate a characteristic of the data tag. For example, a customer exclusive data tag identifier element may indicate that its corresponding data tag is related to data that is specifically associated with the consumer. A length element may indicate the length of the value element in the data tag, or could indicate the length of the data tag itself. For example, a length element, which has the value “4” may indicate that the value element may have four characters. The length element advantageously indicates the size of its corresponding value element so that a computer apparatus that reads the data tag will know how large the data tag will be. Lastly, a value element can be a substantive value associated with the data tag. For example, a consumer's phone number could be a substantive value and can be an example of user exclusive data or customer exclusive data. As an illustration, a data tag including a customer's phone number might be 99105555555. “99” might be a tag identifier element indicating a phone number. “10” might be an indication of the length of the value. “5555555555” might be a value corresponding to a phone number.
  • [0021]
    In embodiments of the invention, the payment process can include the reading of additional data from a contactless portable consumer device, or other type of consumer device, in the form of data tags from the portable consumer device. This additional data can be included in a supplementary data field such as Field 55. Additional transaction information can be included in the authorization request message to the issuer and can be utilized at any node of the system to provide new services (i.e. used by the merchant, acquirer, payment processing organization, issuer, or other third party service providers). The issuer may provide additional services in addition to the returning of the traditional authorization or decline of the transaction at the time of the purchase.
  • [0022]
    Embodiments of the invention include the use of a user exclusive data tag. The user exclusive data tag may include user exclusive data. More specifically, the user exclusive data tag may be a customer exclusive data tag. Many of the specific examples below describe the use of customer exclusive data tags and customer exclusive data. It is understood that the users of embodiments of the invention need not be strictly customers that purchase goods and services at a merchant.
  • [0023]
    User exclusive data (or customer exclusive data) may be in any suitable form. User exclusive data may relate to a characteristic of a portable consumer device that the user is using (e.g., a phone number associated with a having a payment function), or may relate to a characteristic (e.g., the consumer's annual income) or preferences (e.g., a preference for receiving alerts when transactions are conducted) of the consumer. Typically, the user exclusive data is uniquely associated with the particular user (e.g., a consumer). The types of services that can be produced after analyzing the user exclusive data may include rewards, authentication, risk analysis, etc. Further, the user exclusive data may correspond to the “value element” in the tag that is described above.
  • [0024]
    A “customer exclusive data tag” may be used to include customer exclusive data. Customer exclusive data may be personalized on the portable consumer device prior to issuance and/or derived by the device at the point of sale and placed into this data tag in advance of point of sale authorization. The contents of this tag are then forwarded from the point of sale to the issuer, via a payment processing network, in the supplementary data field as part of an authorization request message.
  • [0025]
    Table 1 has samples of the types of data that may be included in the customer exclusive data tag. Information from this table, supplied within the authorization request message to the issuer, may be useful to service providers such as merchants, payment processing organizations and card issuers for a variety of purposes. Below are some example business uses for this data.
  • [0000]
    TABLE 1
    Examples of Customer Exclusive Data to be Included in a Customer
    Exclusive Tag
    Cell Phone Number A phone number may be included in
    a customer exclusive data tag and
    may be used by a service provider to
    send authentication request
    messages to the phone associated
    with the phone number; there is no
    need to store this data at the service
    provider.
    A phone number may be included in
    a customer exclusive data tag and
    provides the service provider with the
    ability to provide text, coupons, or
    marketing elements to the phone
    associated with the phone number
    during a transaction.
    Email address An e-mail address may be included
    in a customer exclusive data tag and
    may be used by a service provider to
    provide for authentication and
    notification messages to a consumer
    via e-mail.
    Loyalty number(s) of airline Loyalty numbers may be included in
    frequent flyer, hotel programs, a customer exclusive data tag and
    car rental agencies, etc may be used by a service provider
    for reporting, assignment of points,
    and other services.
    Risk or authentication data Risk or authentication data may be
    included in a customer exclusive
    data tag and may be used by a
    service provider to provide
    challenge/response information.
    Alternate ID for transit use other An alternate ID or identifier such as a
    than PAN transit identifier may be included in a
    customer exclusive data tag and may
    be used by a service provider to
    determine if it is on a transit hot list.
    This number can be sent in an
    authorization request message and
    cross referenced to the real PAN for
    payment. A transit agency can utilize
    this number in the clear within their
    systems. This application can be
    limited to a transit MCC (merchant
    category code).
    Transit fare data Transit fare data may be included in
    a customer exclusive data tag and
    may be used as a type of monthly
    pass that is good for a specified
    period for a specific agency (e.g., on
    a mobile device, with updates over-
    the-air or OTA)
    Prepaid data Prepaid value data may be included
    in a customer exclusive data tag and
    may be kept in-sync with an issuer's
    data. If the portable consumer
    device is a mobile device such as a
    phone, it can be updated over-the-
    air. Prepaid value data could also be
    displayed on the phone. Off-line
    transit readers could also know if the
    prepaid device has value.
    Government identifying A driver's license, passport number,
    number(s) or registered travel information may
    be included in a customer exclusive
    data tag. This information may be
    used to authenticate the consumer
    and may be used for other purposes.
    Other affiliations Affiliation information can be included
    in a customer exclusive data tag and
    may be read by reader for entry at an
    event such as a ball game, race
    track, church, bingo hall, etc.
    Preferences Preference information for airlines
    (e.g., window or aisle seat), hotels
    (e.g., queen or double bed), or
    restaurants (e.g., smoking or non
    smoking) can be included in a
    customer exclusive data tag. This
    information may be read by a
    merchant or other service provider
    and customized services may be
    provided to the consumer.
    Cardholder name An encrypted or obscured name or
    other information that only one or
    multiple merchants can decipher can
    be included in a customer exclusive
    data tag. This information may be
    used for purposes such as
    authentication.
    Internet encrypted PAN A primary account number (PAN), in
    encrypted or unencrypted form, may
    be included in a customer exclusive
    data tag, which is located in a
    supplemental data field. An alternate
    PAN may be sent in the normal PAN
    data field.
    Other encrypted data A customer exclusive data tag may
    include other encrypted data as
    defined for a particular service.
  • [0026]
    Exemplary systems and methods using these data tags are provided below.
  • [0027]
    I. Exemplary Systems
  • [0028]
    A system according to an embodiment of the invention is shown in FIG. 1.
  • [0029]
    FIG. 1 shows a system 20 that can be used in an embodiment of the invention. The system 20 includes a merchant 22 and an acquirer 24 associated with the merchant 22. In a typical payment transaction, a consumer such as consumer A 30(a) may purchase goods or services at the merchant 22 using a portable consumer device such as portable consumer device A 32-1. The consumer may be an individual, or an organization such as a business that is capable of purchasing goods or services. The acquirer 24 can communicate with an issuer 28 via a payment processing network 26.
  • [0030]
    As used herein, an “issuer” is typically a business entity (e.g., a bank) which maintains financial accounts for the consumer and often issues a portable consumer device such as a credit or debit card to the consumer. A “merchant” is typically an entity that engages in transactions and can sell goods or services. An “acquirer” is typically a business entity (e.g., a commercial bank) that has a business relationship with a particular merchant or other entity. Some entities can perform both issuer and acquirer functions. Embodiments of the invention encompass such single entity issuer-acquirers.
  • [0031]
    In FIG. 1, three consumers, consumer A 30(a), consumer B 30(b), and consumer C 30(c) are illustrated. Consumer A 30(a) can use at least two different types of portable consumer devices including consumer device A 32-1 and portable consumer device B 32-2. In one example, consumer device A 32-1 may be in the form of a phone, while portable consumer device B 32-2 may be in the form of a card. The consumer device A 32-1 may consequently be used to communicate with the issuer 28 via a telecommunications gateway 60, a telecommunications network 70, and a payment processing network 26. The different consumer devices A 32-1 and B 32-2 could be linked to the same issuer account number, or could be linked to respectively different issuer account numbers. Consumer B 30(b) is another consumer that is illustrated in FIG. 1. Consumer B 30(b) may use a specific type of consumer device C 32-3 such as a key fob. Lastly, consumer C 30(c) may use a specific type of consumer device 324 such as a personal computer to communicate with the merchant 22 and other parties including the payment processing network 26 and the issuer 28 via the Internet 72.
  • [0032]
    The consumer devices according to embodiments of the invention may be in any suitable form. In some embodiments, the consumer devices are portable in nature and may be portable consumer devices. Suitable portable consumer devices can be hand-held and compact so that they can fit into a consumer's wallet and/or pocket (e.g., pocket-sized). They may include smart cards, ordinary credit or debit cards (with a magnetic strip and without a microprocessor), keychain devices (such as the Speedpass™ commercially available from Exxon-Mobil Corp.), etc. Other examples of portable consumer devices include cellular phones, personal digital assistants (PDAs), pagers, payment cards, security cards, access cards, smart media, transponders, and the like. The portable consumer devices can also be debit devices (e.g., a debit card), credit devices (e.g., a credit card), or stored value devices (e.g., a stored value card).
  • [0033]
    Each consumer device may comprise a body, and a memory comprising a computer readable medium disposed on or within the body. The computer readable medium may comprise code for a form factor indicator element coupled to the body. The form factor indicator element may be in a form factor indicator tag. The computer readable medium may also comprise code for one or more customer exclusive data tags (described above). In addition, the consumer device may also include a processor coupled to the memory, where greater functionality and/or security are desired.
  • [0034]
    Other types of consumer devices may include devices that are not generally carried by consumers to make purchases. An example of a consumer device of this type may be a desktop computer terminal.
  • [0035]
    The payment processing network 26 may include data processing subsystems, networks, and operations used to support and deliver authorization services, exception file services, and clearing and settlement services. An exemplary payment processing network may include VisaNet™. Payment processing networks such as VisaNet™ are able to process credit card transactions, debit card transactions, and other types of commercial transactions. VisaNet™, in particular, includes a VIP system (Visa Integrated Payments system) which processes authorization requests and a Base II system which performs clearing and settlement services.
  • [0036]
    The payment processing network 26 may include a server computer. A server computer is typically a powerful computer or cluster of computers. For example, the server computer can be a large mainframe, a minicomputer cluster, or a group of servers functioning as a unit. In one example, the server computer may be a database server coupled to a Web server. The payment processing network 26 may use any suitable wired or wireless network, including the Internet.
  • [0037]
    The server computer in the payment processing network 26 may comprise code for receiving, at the server computer, an authorization request message comprising customer exclusive data, where the customer exclusive data was previously stored in a consumer device; code for analyzing the authorization request message; and code for performing additional processing based on the customer exclusive data.
  • [0038]
    The merchant 22 may also have, or may receive communications from, an access device 34 that can interact with the portable consumer device 32. The access devices according to embodiments of the invention can be in any suitable form. Examples of access devices include point of sale (POS) devices, cellular phones, PDAs, personal computers (PCs), tablet PCs, handheld specialized readers, set-top boxes, electronic cash registers (ECRs), automated teller machines (ATMs), virtual cash registers (VCRs), kiosks, security systems, access systems, and the like.
  • [0039]
    If the access device 34 is a point of sale terminal, any suitable point of sale terminal may be used including card readers. The card readers may include any suitable contact or contactless mode of operation. For example, exemplary card readers can include RF (radio frequency) antennas, magnetic stripe readers, etc. to interact with the portable consumer devices 32.
  • [0040]
    In a typical purchase transaction, a consumer such as consumer A 30(a) purchases a good or service at the merchant 22 using a portable consumer device such as portable consumer device B 32-2, which may be in the form of a credit card. The consumer's portable consumer device B 32-2 can interact with an access device 34 such as a POS (point of sale) terminal at the merchant 22. For example, the consumer 30 may take the credit card and may swipe it through an appropriate slot in the POS terminal. Alternatively, the POS terminal may be a contactless reader, and the portable consumer device B 32-2 may be a contactless device such as a contactless card.
  • [0041]
    An authorization request message is then forwarded to the acquirer 24. After receiving the authorization request message, the authorization request message is then sent to the payment processing network 26. The payment processing network 26 then forwards the authorization request message to the issuer 28 of the portable consumer device B 32-2.
  • [0042]
    After the issuer 28 receives the authorization request message, the issuer 28 sends an authorization response message back to the payment processing network 26 (step 56) to indicate whether or not the current transaction is authorized (or not authorized). The payment processing network 26 then forwards the authorization response message back to the acquirer 24. The acquirer 24 then sends the response message back to the merchant 22.
  • [0043]
    After the merchant 22 receives the authorization response message, the access device 34 at the merchant 22 may then provide the authorization response message for consumer A 30(a). The response message may be displayed by the access device 34, or may be printed on a receipt.
  • [0044]
    At the end of the day, a normal clearing and settlement process can be conducted by the payment processing network 26. A clearing process is a process of exchanging financial details between and acquirer and an issuer to facilitate posting to a consumer's account and reconciliation of the consumer's settlement position. Clearing and settlement can occur simultaneously.
  • [0045]
    II. Exemplary Consumer Devices, Access Devices, and Computer Apparatuses
  • [0046]
    FIG. 2( a) shows a block diagram of another phone 32′ that can be used in embodiments of the invention. The exemplary wireless phone 32′ may comprise a computer readable medium and a body as shown in FIG. 2( a). The computer readable medium 32(b) may be present within the body 32(h), or may be detachable from it. The body 32(h) may be in the form a plastic substrate, housing, or other structure. The computer readable medium 32(b) may be in the form of (or may be included in) a memory that stores data (e.g., data relating to issuer specific payment services) and may be in any suitable form including a magnetic stripe, a memory chip, etc. The memory preferably stores information such as financial information, transit information (e.g., as in a subway or train pass), access information (e.g., as in access badges), etc. Financial information may include information such as bank account information, a bank identification number (BIN), credit or debit card number information, account balance information, expiration date, consumer information such as name, date of birth, etc. Any of this information may be transmitted by the phone 32′.
  • [0047]
    In some embodiments, information in the memory may also be in the form of data tracks that are traditionally associated with credits cards. Such tracks include Track 1 and Track 2. Track 1 (“International Air Transport Association”) stores more information than Track 2, and contains the cardholder's name as well as account number and other discretionary data. This track is sometimes used by the airlines when securing reservations with a credit card. Track 2 (“American Banking Association”) is currently most commonly used. This is the track that is read by ATMs and credit card checkers. The ABA (American Banking Association) designed the specifications of this track and all world banks must abide by it. It contains the cardholder's account, encrypted PIN, plus other discretionary data.
  • [0048]
    The phone 32′ may further include a contactless element 32(g), which is typically implemented in the form of a semiconductor chip (or other data storage element) with an associated wireless transfer (e.g., data transmission) element, such as an antenna. Contactless element 32(g) is associated with (e.g., embedded within) phone 32 and data or control instructions transmitted via a cellular network may be applied to contactless element 32(g) by means of a contactless element interface (not shown). The contactless element interface functions to permit the exchange of data and/or control instructions between the mobile device circuitry (and hence the cellular network) and an optional contactless element 32(g).
  • [0049]
    Contactless element 32(g) is capable of transferring and receiving data using a near field communications (“NFC”) capability (or near field communications medium) typically in accordance with a standardized protocol or data transfer mechanism (e.g., ISO 14443/NFC). Near field communications capability is a short-range communications capability, such as RFID, Bluetooth™, infra-red, or other data transfer capability that can be used to exchange data between the phone 32′ and an interrogation device. Thus, the phone 32′ is capable of communicating and transferring data and/or control instructions via both cellular network and near field communications capability.
  • [0050]
    The phone 32′ may also include a processor 32(c) (e.g., a microprocessor) for processing the functions of the phone 32 and a display 32(d) to allow a consumer to see phone numbers and other information and messages. The phone 32′ may further include input elements 32(e) to allow a consumer to input information into the device, a speaker 32(f) to allow the consumer to hear voice communication, music, etc., and a microphone 32(i) to allow the consumer to transmit her voice through the phone 32′. The phone 32′ may also include an antenna 32(a) for wireless data transfer (e.g., data transmission).
  • [0051]
    FIG. 3 shows a block diagram of an access device 34 according to an embodiment of the invention. The access device 34 comprises a processor 34(c) operatively coupled to a computer readable medium 34(d) (e.g., one or more memory chips, etc.), input elements 34(b) such as buttons or the like, a reader 34(a) (e.g., a contactless reader, a magnetic stripe reader, etc.), an output device 34(e) (e.g., a display, a speaker, etc.) and a network interface 34(f). The computer readable medium may comprise instructions or code, executable by a processor. The instructions may include instructions for reading a user exclusive data tag or user exclusive data from a consumer device, generating an authorization request message with the user exclusive data tag or the user exclusive data, and sending the authorization request message including the user exclusive data tag or the user exclusive data to a service provider such as an issuer or payment processing network.
  • [0052]
    The various participants and elements in FIG. 1 may operate one or more computer apparatuses (e.g., a server computer) to facilitate the functions described herein. Any of the elements in FIG. 1 may use any suitable number of subsystems to facilitate the functions described herein. Examples of such subsystems or components are shown in FIG. 4. The subsystems shown in FIG. 4 are interconnected via a system bus 775. Additional subsystems such as a printer 774, keyboard 778, fixed disk 779 (or other memory comprising computer readable media), monitor 776, which is coupled to display adapter 782, and others are shown. Peripherals and input/output (I/O) devices, which couple to I/O controller 771, can be connected to the computer system by any number of means known in the art, such as serial port 777. For example, serial port 777 or external interface 781 can be used to connect the computer apparatus to a wide area network such as the Internet, a mouse input device, or a scanner. The interconnection via system bus allows the central processor 773 to communicate with each subsystem and to control the execution of instructions from system memory 772 or the fixed disk 779, as well as the exchange of information between subsystems. The system memory 772 and/or the fixed disk 779 may embody a computer readable medium.
  • [0053]
    II. Exemplary Methods
  • [0054]
    Methods according to embodiments of the invention can be described with respect to FIGS. 1 and 5. Generally, the method may include obtaining a portable consumer device comprising a body, and a memory comprising a computer readable medium disposed on or within the body, the computer readable medium comprising user exclusive data; and using the portable consumer device to interact with an access device, wherein the access device thereafter generates and sends an authorization request message to an issuer associated with the portable consumer device. A server computer at the issuer or the payment processing network may thereafter analyze the authorization request message and the user exclusive data in the authorization request message. The server computer may thereafter perform additional processing using the user exclusive data.
  • [0055]
    Prior to using the customer exclusive data tag with customer exclusive data in transactions, a portable consumer device may be loaded with the customer exclusive data. The customer exclusive data may be representative of the actual data (e.g., a phone number encoded on a payment card) or may be representative of a code or other data element that is linked to the actual data. As an example of the latter case, a code such as the letter “1” may be linked to an instruction such as sending an alert to the consumer's phone. When a service provider server computer determines that a particular data tag has the number “1”, it may retrieve the instruction to send the alert to the consumer's phone and may thereafter initiate this function.
  • [0056]
    In one embodiment, the customer exclusive data may be provided to a service provider such as a merchant, an organization that operates the payment processing network, or an issuer. It may be provided to the service provider in any suitable manner. If the service provider is, for example, an organization that operates the payment processing network 26 or the issuer 28, then the consumer (e.g., consumer C 30(c)) may contact a server computer in the payment processing network 26 or at the issuer 28 via the Internet 72, using a standard computing device (e.g., consumer device C 32-4) operating a standard operating system (e.g., a Windows™ based operating system) and using a standard browser (Internet Explorer)™. The consumer can then provide customer exclusive data to the payment processing network 26 or the issuer 28. In some embodiments, after receiving the customer exclusive data, the issuer 28 could issue one or more portable consumer devices to the consumer with the customer exclusive data stored in their associated memories. Alternatively, if the consumer devices can receive data (e.g., as in the case of phones or computers), then the customer exclusive data can be send to the consumer devices and then stored in them. In yet another embodiment, the consumer data may be loaded on to the consumer devices by the user using external devices such as access devices. For example, a consumer could take a standard payment card with a re-writeable memory to an access device that can write the customer exclusive data to the standard payment card. In yet another embodiment, the consumer device itself can generate the customer exclusive data. For example, the consumer device can generate a dCVV (dynamic card verification value) and this data can be used as customer exclusive data. Regardless of how the consumer data is loaded on to the consumer's consumer device, the consumer data may include any of the particular type or amount of consumer-specific data including any of the types of data described in FIG. 1.
  • [0057]
    After the consumer data is loaded into the consumer device, it may be used in a transaction such as payment transaction. In an exemplary embodiment, a consumer may use a portable consumer device including a customer exclusive data tag. Illustratively, a consumer A 30(a) may first use his portable consumer device A 32-1 to purchase a good or service at a merchant 22. The portable consumer device A 32-1 may be in the form of a phone with a contactless element (as described above with respect to FIG. 2( a)). When making the purchase, the consumer A 30(a) may pass the portable consumer device A 32-1 by the access device 34, or may otherwise interact with it (step 202). The customer exclusive data tag may be stored in a memory in the portable consumer device A 32-1. The customer exclusive data tag and account information such as the account number associated with the issuer 28 may pass from the portable consumer device A 32-1 to the access device 34. A reader in the access device 34 can read the customer exclusive data tag and the account information, and a processor in the access device 34 can generate an authorization request message including the form factor indictor tag, the account information (e.g., a BIN, expiration date, etc.), a merchant code (e.g., a merchant category code), and the price associated with the good or service purchased. The access device 34 may then send the authorization request message to the payment processing network 26 via the merchant's acquirer 24 (step 204). Although customer exclusive data is included in a customer exclusive data tag in this embodiment, customer exclusive data (or user exclusive data) could be sent in an authorization request message without being in a tag in other embodiments of the invention. In addition, in some embodiments, the customer exclusive data may be stored in the consumer device, and the access device may subsequently receive the customer exclusive data and may form a customer exclusive data tag with the customer exclusive data.
  • [0058]
    A server computer in the payment processing network 26 can then receive (step 206) and analyze the authorization request message. It can perform additional processing (step 208) using the customer exclusive data tag, before sending the authorization request message on to the issuer 28 for approval. For example, the customer exclusive data may include the consumer's mobile phone number and may also include a preference for receiving alert messages for transactions that are conducted by the consumer. The additional processing in this example comprises initiating the sending of a notification message to the consumer device (e.g., portable consumer device A 32-1). The notification message may indicate that the current transaction is being conducted. Additional processing may not only involve sending messages after analyzing customer exclusive data. Other additional processing steps may involve adding points or other benefits to user or consumer accounts, sending messages to entities other than the consumer, performing the transaction in a specific manner that is different than a normal transaction, etc. Yet other specific examples of additional processing (step 208) are provided below.
  • [0059]
    Although a server at the payment processing network 26 is described as performing additional processing in this and in other examples in this application, it is understood that other entities including the merchant 22, acquirer 24, issuer 28, or a third party processor may perform such additional processing using its own server computer.
  • [0060]
    The authorization request message is then forwarded to the issuer 28 for approval (step 210). The issuer 28 may then approve or deny the transaction, depending on whether there is sufficient credit and/or sufficient funds in the consumer A's account. After this, the issuer 28 sends an authorization response message back to access device 34 via the acquirer 24 and the payment processing network 26 (step 212).
  • [0061]
    Examples of New Services Resulting from Extra Data Including Customer Exclusive Data and Form Factor Indicator Tags
  • [0062]
    Table 1 above has samples of the types of data that may be included in the customer exclusive data tag. Information from Table 1, supplied within the authorization request message to the issuer, may be useful to service providers such as payment processing organizations and card issuers for a variety of purposes. Below are some example uses for this data. The specific examples provided below relate to the use of a server computer in a payment processing network as the device which receives an authorization request message and then performs additional processing. Embodiments of the invention, are not, however, limited to this. Embodiments of the invention could also be performed in other ways. For example, instead of the payment processing network 26, the issuer 28, or a third party payment processor may perform the functions performed by the payment processing network 26.
  • [0063]
    Transaction Notification and Control:
  • [0064]
    In one embodiment of the invention, a service provider such as an issuer 28 or payment processing network 26 could establish a transaction notification service where the phone, text, or email is used to validate a transaction. For example, a parent could give his card to his child and ask to be notified any time his card is used, anytime a transaction exceeds a predetermined threshold (e.g., $25), or anytime the merchant has a specified characteristic (e.g. a liquor store). Notification flags could be of any type, value, merchant name or type, location, count, etc. The notification could be sent to a phone, or other suitable device.
  • [0065]
    Referring to FIG. 1, the consumer A 30(a) may be the child and may use a payment card (portable consumer device B 30-2). The payment card (portable consumer device B 30(b)) may store a customer exclusive data tag with notification data. The notification data may include a code that indicates that message should be sent to a phone (portable consumer device A 32-1) if a purchase is above $100 and/or is made at a prohibited merchant (e.g., a liquor store). When the child makes a purchase with the card (portable consumer device B 30-2) at the merchant 22, the child uses the card (portable consumer device B 30-2) to interact with the access device 34. A processor in the access device 34 then receives data including the customer exclusive data tag from the card 32-2 and generates an authorization request message which is then sent to the issuer 38 via the acquirer 24, and payment processing network 26. Before it is received at the issuer 28, a server computer in the payment processing network 26 may analyze the authorization request message and the customer exclusive data tag. Information in the customer exclusive data tag may indicate that an alert message is to be sent to the phone (portable consumer device A 32-1) if the amount of the transaction exceeds $100. The information in the customer exclusive data tag may be in the form of a code that corresponds to an instruction to send a message to the phone (portable consumer device A 32-1) if the transaction exceeds $100. This information may be stored in a database at the payment processing network 26. If the amount of the transaction exceeds $100, an alert message is sent from the payment processing network 26 to the telecommunications network 70, and to the phone (portable consumer device A 32-1). In this example, the sending of the alert message may involve additional processing.
  • [0066]
    In a similar manner, the service provider (e.g., an organization that operates the payment processing network 26 or the payment processing network 26 itself) could also establish a notification service for a corporate or fleet card. An employer or supervisor can give a corporate card to an employee for the purchase of gas or the purchase of other necessities. For example, the above-described authorization request message may include data that represents an instruction to send an alert message to the employee's supervisor, each time or under specific conditions specified by the employer or supervisor. This could allow for notification and control on specific devices, or groups of devices as consolidated by the issuer.
  • [0067]
    In yet another example, fleet card accounting is possible based on parameters established in a host computer system. Using accounting preferences as established by customer exclusive data from the consumer device, logging, receipts, notification, and accounting can be done per device or as consolidated based on a master account. The master account may be held by an employer and each employee of the employer may operate a different consumer device. Transaction data associated with purchases made by each consumer device could be routed to the employer's computer system.
  • [0068]
    In embodiments of the invention, the transaction control service could be of a passive or active type. In the passive mode, transactions are automatically allowed or disallowed based on pre-established parameters held on the consumer device, type, value, merchant name or type, location, count, etc. No notification is necessary. This could be used to stop this one transaction or all future transactions if the parameters are met. In the active mode, notification by e-mail, text message, or phone call is made to ask for the transaction to be allowed or disallowed. The decision or control mechanism is included in the transaction flow.
  • [0069]
    Note that in these embodiments, a consumer does not need to register for the alerts service, since an issuer can load the consumer's portable consumer device with the consumer's phone number. This advantageously can save the consumer time and effort.
  • [0070]
    Electronic Receipts or Statements:
  • [0071]
    In other embodiments of the invention, a service provider such as the payment processing network 26 or the issuer 28 could establish an electronic receipt service where the phone or other device is used as a place to receive a receipt. For example, a flag indicating that a receipt is required could be included in the customer exclusive data in an authorization request message which passes from the merchant 22 to the payment processing network 26. For some merchant types, a receipt may not be available (such as transit or other high speed point of sale environment). As an additional processing step, the receipt could be sent from the payment processing network 26 to a phone (e.g., portable consumer device A 32-1) as a text message or email.
  • [0072]
    The electronic receipt could be sent, for example, in a pre-defined format consistent with specific software for expense reports. For example, the customer exclusive data tag may include customer exclusive data which indicates a preference for electronic receipts in a format that is compatible with Microsoft Excel™. Alternatively, the receipt could be, for example, of any free-form format for display on a phone screen. Which type of receipt to send could be included as part of the data from the portable consumer device in the customer exclusive data.
  • [0073]
    Monthly statement preferences could be as defined on the device. The customer exclusive data could indicate that monthly paper statements should be mailed, or could indicate that electronic statements should be e-mailed.
  • [0074]
    Loyalty:
  • [0075]
    In other embodiments of the invention, there could be information about loyalty programs included on the portable consumer device, such as, for example, loyalty program identification and participation information. The data in the consumer device (portable consumer device B 32-2) could tell the merchant 22 how to process data as preferred by the cardholder. For example, the customer exclusive data tag in an authorization request message may indicate that the cardholder (e.g., consumer A 30(a)) may choose to use points before charges are made in cash. As noted above, this authorization request message may be sent from the access device 34 to the payment processing network 26 via the acquirer 24. A server computer in the payment processing network 26 could then apply points to the particular transaction being conducted and could then re-format the authorization request message to the issuer 26 for the difference between the transaction price and the value of the points. In another example, it may be possible for the payment processing network 26 to apply one program first in advance of another such as airline mileage, rather than rental car points. In these cases, the data held on the consumer device (e.g., portable consumer device A 32-1) is used by the merchant 22.
  • [0076]
    Transaction Security:
  • [0077]
    Today, in a dynamic CVV (card verification value) process, a device application transaction counter (ATC) is sent in the clear within the authorization request message from the access device 34 at the merchant 22 to the issuer 28. The information is then used by the issuer 28 to detect fraud. For example, if the ATC does not match the ATC at the issuer, then this may indicate that there is fraud. It is also possible for transactions to be recorded and viewed, and under certain scenarios, it may be possible to commit fraud because the security data is not hidden.
  • [0078]
    In embodiments of the invention, using encryption techniques, customer exclusive data could include the ATC in encrypted format as it is provided by the portable consumer device (portable consumer device A 32-1) to the access device 34. The access device 34 can then transmit the authorization request message to the payment processing network 26 and the issuer 28. This can prevent a would-be fraudster from seeing or utilizing this data. Additionally, there is much more space within the customer exclusive data tag to allow for a longer cryptogram (as compared to conventional message protocols), thereby making the transaction more secure.
  • Reloadable Prepaid Account:
  • [0079]
    Reloadable prepaid cards are sometimes first issued with a temporary card prior to enrollment. After enrollment, a personalized embossed card is typically sent as a replacement for the temporary card. Some interesting opportunities exist when the personalized card is issued with customer exclusive data. For instance, a customer exclusive data tag could indicate the mechanism for account replenishment. For example, account replenishment can occur through a monthly payroll, or it can be topped up against another bank account, and an indicator of this may be included in a customer exclusive data tag that is sent in an authorization request message from the access device 34 to the payment processing network 26 and the issuer 28. The customer exclusive data tag could be used to indicate how to notify the cardholder (e.g., consumer A 30(a)) when the account balance is getting low (i.e. through email, text message, phone call, etc). In another example, a prepaid card could be issued to a child, and an account associated with the prepaid card can be topped up with funds from the parent's account. The top up mechanism could be included on the child's card. When the child's card is used at the access device 34, an authorization request message including those top up preferences may be sent to the prepaid issuer 28.
  • [0080]
    Proxy Account Information:
  • [0081]
    For purposes of security, there may be instances where the primary account number (PAN) can be masked during a payment transaction. For example, transit fare collection could be an example where the real PAN can be masked due to the off-line nature of bus fare transactions and the need to store cardholder information, possibly for multiple hours on a bus or other mode of transportation. The customer exclusive data could be used in an authorization request message to hold a proxy account number that is linked to the real PAN in the issuer host system. The proxy account number is read and used by all nodes in the payment system. The proxy account could be limited for use in specific merchant types (like transit). For example, the authorization request message could be sent from the access device 34 to the issuer 28 via the acquirer 24 and the payment processing network 26. Each of these nodes may see and use the proxy account number. However, the real PAN may be customer exclusive data that is determined and analyzed by a server computer in the payment processing network 26 or the issuer 28. Normal transaction processing can take place after the real PAN is determined by the payment processing network 26 or the issuer 28.
  • [0082]
    Multi-Application:
  • [0083]
    College or commercial campus environments many times require multiple applications with data peculiar to each application. The customer exclusive data in an authorization request message could be used to hold other account data and preferences for such things as student ID, payment preferences, dorm access information or ID, notification information, age verification and identity, etc.
  • [0084]
    Version Control:
  • [0085]
    At times the version of a card or application may be important for variety of reasons. For example, if version 1 of a card or application uses one type of encryption and version 2 of a card or application uses another type of encryption, it would be desirable for the issuer and other service providers to know what card type is being used. This information could be included in the customer exclusive data to indicate to the payment nodes what version of the card was used.
  • [0086]
    Form Factor Indictor and Customer Exclusive Data Tags Used Together
  • [0087]
    Another type of data tag that can be used in conjunction with the customer exclusive data tag is a “form factor indicator data tag.” As this data is forwarded to the payment processing network and the issuer, the information may be used as necessary by service providers that recognize the data for a particular service. The definition of the data within this tag may be standardized or may be specific to a particular issuer's definition, and may be in the clear or encrypted.
  • [0088]
    Payment transactions and other transactions can be initiated by portable consumer devices other than traditional card form factors. Mini-cards, micro tags, key FOBs, cell phones, watches, and other key chain devices can be used to initiate a payment transaction at the point of sale.
  • [0089]
    The form factor indicator tag is available to indicate the capabilities of the device used to initiate the transaction at the point of sale. It is possible for the issuer to personalize one character of track data with values of 1 to 9 to indicate the device type. It is recognized that 9 values may not be sufficient to fully define not only the form factor of the device, but other inherent capabilities that the device may possess. Although embodiments of the invention are not limited to the size of a tag, the form factor indicator tag can be sized to 4 bytes (8 hex characters) and can be refined with more definition than is available with one character in track data. The form factor indicator tag can be transmitted in a supplementary data field in an authorization request message from the point of sale to the issuer during an authorization process.
  • [0090]
    A form factor indicator tag may include a form factor indicator element, a device security features element, and a device communications features element. The form factor indicator element may include information about the particular form factor of the portable consumer device being used. The device security features element may indicate the type of security features that are present on the particular portable consumer device. Lastly, the device communications feature element may include information about the particular communication features present in the device.
  • [0091]
    Table 2 provides examples of some types of indications that may be utilized or defined with the form factor indicator tag. As illustrated below, the form factor indicator tag may include a form factor indicator element, a device security features element, other data elements, and a device communications technology element.
  • [0000]
    TABLE 2
    Examples of data that can be present in Form
    Factor Indicator Tag Data
    1st byte Form factor indicator Full size card
    Mini card
    Micro tag
    Mobile device (phone)
    PDA
    Watch
    2nd byte Device security Signature panel
    features element Hologram
    Embossing
    Biometric
    CVV (card verification value)
    CVV2 (card verification value 2)
    dCVV (dynamic card verification value)
    CVN 17 (card verification number 17)
    CVN 10 (card verification number 10)
    SDA (static data authentication)
    DDA (dynamic data authentication)
    Text or email capable
    Pre-registered with issuer for
    authentication messaging
    Crypto coprocessor capable
    3rd byte Other data element Other data
    4th byte Device ISO 14443 (Proximity) including NFC
    communications ISO 15693 (Vicinity)
    technology element Infra Red
    Bluetooth
    GSM or other wide area cellular
    network
  • [0092]
    Additional details regarding the use of Customer Exclusive Data Tags are provided in U.S. patent application Ser. No. ______ entitled “Device Including Form Factor Indicator,” which is being filed on the same day as the present application (Attorney Docket No. 16222U-041710US) and which is herein incorporated by reference in its entirety for all purposes.
  • [0093]
    The form factor indicator tag can be used to initiate a transaction at the point of sale and may be used by service providers for a variety of purposes. It can be used alone or in combination with the customer exclusive data tag.
  • [0094]
    Referring to FIGS. 1 and 6, a consumer A 30(a) may first use his portable consumer device A 32-1 to purchase a good or service at a merchant 22. The portable consumer device A 32-1 may be in the form of a phone with a contactless element (as described above with respect to FIG. 2( a). When making the purchase, the consumer A 30(a) may pass the portable consumer device A 32-1 by the access device 34, or may otherwise interact with it (step 302). The form factor indicator tag may be stored in a memory in the portable consumer device A 32-1. The form factor indicator tag and account information such as the account number associated with the issuer 28 may pass from the portable consumer device A 32-1 to the access device 34. In addition, a customer exclusive data tag may have been previously stored in the memory of the portable consumer device A 32-1 and it may pass to the access device 34. A reader in the access device 34 can read the customer exclusive data tag, and the form factor indicator tag and the account information, and a processor in the access device 34 can generate an authorization request message including the customer exclusive data tag and the form factor indictor tag, the account information, the merchant code, and the price associated with the good or service purchased. The access device 34 may then send the authorization request message to the payment processing network 26 via the merchant's acquirer 24 (step 304).
  • [0095]
    A server computer in the payment processing network 26 can then receive (step 306) and analyze the authorization request message and can perform additional processing (step 308) using the form factor indicator tag and the customer exclusive data tag, before sending the authorization request message on to the issuer 28 for approval.
  • [0096]
    The authorization request message is then forwarded to the issuer 28 for approval (step 310). The issuer 28 may then approve or deny the transaction, depending on whether there is sufficient credit and/or sufficient funds in the consumer A's account. After this, the issuer 28 sends an authorization response message back to access device 34 via the acquirer 24 and the payment processing network 26 (step 312).
  • [0097]
    In one specific example, the form factor indicator tag in the authorization request message may indicate that the consumer device is a mobile phone (byte 1 of the tag). The customer exclusive data tag may include the phone number of the mobile phone. The server computer in a payment processing network 26 or in another location can then send an authentication message to the consumer device 32-1 by SMS, text, or e-mail as provided in a customer exclusive data tag in the authorization request message. In another example, it is possible to take the form factor indicator from byte 1 of the form factor indicator tag, and then use the consumer device to encrypt it for security purposes. It is then possible to send an authorization request message with the encrypted indicator tag to the issuer 28 in the customer exclusive data tag. This could be used as an indication that the transaction was not tampered with and that the transaction is authentic.
  • [0098]
    Although a specific example is provided, it is also understood that any of the form factor indicator elements in Table 2 may be combined with any of the customer exclusive data elements in Table 1, in any suitable authorization request message, or other type of message.
  • [0099]
    Embodiments of the invention have a number of advantages. Because user specific data is provided in authorization request messages, normal payment transactions can be conducted and customized in some manner for the particular consumer that is making the current purchase. Each user experience can be different, without requiring the user to expend much effort.
  • [0100]
    Embodiments of the invention are not limited to the above-described embodiments. For example, although separate functional blocks are shown for an issuer, payment processing network, and acquirer, some entities perform (e.g., Discover, AMEX, etc.) all of these functions and may be included in embodiments of invention.
  • [0101]
    Specific details regarding some of the above-described aspects are provided below. The specific details of the specific aspects may be combined in any suitable manner without departing from the spirit and scope of embodiments of the invention.
  • [0102]
    It should be understood that the present invention as described above can be implemented in the form of control logic using computer software in a modular or integrated manner. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will know and appreciate other ways and/or methods to implement the present invention using hardware and a combination of hardware and software
  • [0103]
    Any of the software components or functions described in this application, may be implemented as software code to be executed by a processor using any suitable computer language such as, for example, Java, C++ or Perl using, for example, conventional or object-oriented techniques. The software code may be stored as a series of instructions, or commands on a computer readable medium, such as a random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-ROM. Any such computer readable medium may reside on or within a single computational apparatus, and may be present on or within different computational apparatuses within a system or network.
  • [0104]
    The above description is illustrative and is not restrictive. Many variations of the invention will become apparent to those skilled in the art upon review of the disclosure. The scope of the invention should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the pending claims along with their full scope or equivalents.
  • [0105]
    One or more features from any embodiment may be combined with one or more features of any other embodiment without departing from the scope of the invention.
  • [0106]
    A recitation of “a”, “an” or “the” is intended to mean “one or more” unless specifically indicated to the contrary.
  • [0107]
    All patents, patent applications, publications, and descriptions mentioned above are herein incorporated by reference in their entirety for all purposes. None is admitted to be prior art.
Patent Citations
Cited PatentFiling datePublication dateApplicantTitle
US4114027 *Sep 13, 1976Sep 12, 1978The Mosler Safe CompanyOn-line/off-line automated banking system
US5914472 *Sep 23, 1997Jun 22, 1999At&T CorpCredit card spending authorization control system
US6325285 *Nov 12, 1999Dec 4, 2001At&T Corp.Smart card with integrated fingerprint reader
US6883718 *Feb 27, 2004Apr 26, 2005Imation Corp.Credit card sized memory card with host connector
US7318049 *Aug 17, 2001Jan 8, 2008Gregory Fx IannacciSystem and method for an automated benefit recognition, acquisition, value exchange, and transaction settlement system using multivariable linear and nonlinear modeling
US7356541 *Oct 27, 2000Apr 8, 2008Computer Sciences CorporationProcessing business data using user-configured keys
US7542942 *Mar 11, 2004Jun 2, 2009American Express Travel Related Services Company, Inc.System and method for securing sensitive information during completion of a transaction
US7668754 *Jul 21, 2003Feb 23, 2010Symbol Technologies, Inc.Architecture for secure reverse mobile commerce
US7761374 *Aug 18, 2003Jul 20, 2010Visa International Service AssociationMethod and system for generating a dynamic verification value
US7865141 *Jun 7, 2007Jan 4, 2011Silicon Storage Technology, Inc.Chipset for mobile wallet system
US7954717 *Dec 8, 2010Jun 7, 2011Tyfone, Inc.Provisioning electronic transaction card in mobile device
US7962390 *Jun 5, 2008Jun 14, 2011Visa Usa Inc.Field 55 data relationships
US20030018567 *Jun 4, 2002Jan 23, 2003Orbis Patents Ltd.Business-to-business commerce using financial transaction numbers
US20030121969 *Nov 25, 2002Jul 3, 2003John WankmuellerMethod and system for conducting transactions using a payment card with two technologies
US20030167207 *Jan 10, 2003Sep 4, 2003Berardi Michael J.System and method for incenting payment using radio frequency identification in contact and contactless transactions
US20040128243 *Dec 16, 2003Jul 1, 2004Stephen KavanaghTransaction processing
US20050018670 *Mar 16, 2004Jan 27, 2005Miwa ShigematsuMethod for frame forwarding and network switch
US20050077349 *Dec 14, 2004Apr 14, 2005American Express Travel Related Services Company, Inc.Method and system for facilitating a transaction using a transponder
US20050080726 *Aug 13, 2004Apr 14, 2005First Data CorporationMethod and system for handling method level processing in connection with cardholder account processing
US20060004746 *Aug 4, 2005Jan 5, 2006Kalido LimitedData processing system
US20060022033 *Jul 15, 2005Feb 2, 2006Patrick SmetsMethod and system using a bitmap for passing contactless payment card transaction variables in standardized data formats
US20070055630 *Apr 5, 2006Mar 8, 2007Visa U.S.A.System and method for secured account numbers in proximity devices
US20070094154 *Nov 21, 2006Apr 26, 2007Rau Scott WProcessing transactions using a register portion to track transactions
US20070131761 *Nov 28, 2006Jun 14, 2007Mastercard International IncorporatedTechniques for co-existence of multiple stored value applications on a single payment device managing a shared balance
US20070136211 *Dec 30, 2006Jun 14, 2007Brown Kerry DFinancial transactions with dynamic card verification values
US20070205275 *Mar 6, 2006Sep 6, 2007First Data CorporationPortable point of sale systems and methods
US20070255662 *Mar 30, 2007Nov 1, 2007Obopay Inc.Authenticating Wireless Person-to-Person Money Transfers
US20080027815 *Dec 19, 2006Jan 31, 2008Vivotech, Inc.Methods, systems and computer program products for wireless payment transactions
US20080040285 *Feb 16, 2007Feb 14, 2008John WankmuellerMethod And System For Authorizing A Transaction Using A Dynamic Authorization Code
US20080058014 *Sep 1, 2006Mar 6, 2008Vivotech, Inc.Methods, systems and computer program products for over the air (OTA) provisioning of soft cards on devices with wireless communications capabilities
US20080103968 *Oct 31, 2006May 1, 2008Discover Financial Services LlcRedemption of Credit Card Rewards at a Point of Sale
US20080175390 *Aug 13, 2004Jul 24, 2008Telecom Italia S.P.A.Method of and System For Secure Management of Data Stored on Electronic Tags
US20090083159 *Sep 26, 2007Mar 26, 2009Brian MawForm factor identification
US20090140839 *Feb 6, 2009Jun 4, 2009American Express Travel Related Services Company, Inc.Systems and methods for non-traditional payment using biometric data
US20090265273 *Oct 22, 2009Ncr CorporationTransaction authorization
US20100228668 *Sep 9, 2010Hogan Edward JMethod and System for Conducting a Transaction Using a Proximity Device and an Identifier
US20110145564 *Jun 16, 2011Celltrust CorporationSystems and methods for secure short messaging service and multimedia messaging service
US20110202465 *Aug 18, 2011Ashraf MashhourSystem and method for facilitating point of sale transactions with minimal transfer of sensitive data
US20110276511 *Nov 10, 2011Einar RosenbergApparatus and Method Using Near Field Communications
Referenced by
Citing PatentFiling datePublication dateApplicantTitle
US8090616 *Feb 3, 2009Jan 3, 2012Proctor Jr James ArthurVisual identification information used as confirmation in a wireless communication
US8116749Feb 3, 2009Feb 14, 2012Proctor Jr James ArthurProtocol for anonymous wireless communication
US8364594 *Mar 1, 2011Jan 29, 2013Visa International Service AssociationSystem and method including security parameters used for generation of verification value
US8369842Aug 18, 2011Feb 5, 2013Proxicom Wireless, LlcExchanging identifiers between wireless communication to determine further information to be exchanged or further services to be provided
US8370955Jan 27, 2011Feb 5, 2013Proxicom Wireless, LlcEnforcing policies in wireless communication using exchanged identities
US8374592Aug 18, 2011Feb 12, 2013Proxicom Wireless, LlcExchanging identifiers between wireless communication to determine further information to be exchanged or further services to be provided
US8385896Aug 18, 2011Feb 26, 2013Proxicom Wireless, LlcExchanging identifiers between wireless communication to determine further information to be exchanged or further services to be provided
US8385913 *Feb 3, 2009Feb 26, 2013Proxicom Wireless, LlcUsing a first wireless link to exchange identification information used to communicate over a second wireless link
US8429048Dec 7, 2010Apr 23, 2013Visa International Service AssociationSystem and method for processing payment transaction receipts
US8560447Jul 27, 2011Oct 15, 2013Intuit Inc.Intelligent account selection for electronic bill payment
US8567670Mar 26, 2010Oct 29, 2013Intersections Inc.Dynamic card verification values and credit transactions
US8626658 *Jul 28, 2010Jan 7, 2014Intuit Inc.Methods, systems and apparatus for providing a dynamic account list in an online financial services system
US8650124Mar 25, 2013Feb 11, 2014Visa International Service AssociationSystem and method for processing payment transaction receipts
US8682717Apr 30, 2008Mar 25, 2014Visa U.S.A. Inc.System and method for processing field 55 customer exclusive data
US8738454Jul 23, 2012May 27, 2014Wal-Mart Stores, Inc.Transferring digital receipt data to mobile devices
US8762239Jan 12, 2009Jun 24, 2014Visa U.S.A. Inc.Non-financial transactions in a financial transaction network
US8843398Jul 23, 2012Sep 23, 2014Wal-Mart Stores, Inc.Transferring digital receipt data to mobile devices
US8849698Feb 25, 2013Sep 30, 2014Proxicom Wireless, LlcExchanging identifiers between wireless communication to determine further information to be exchanged or further services to be provided
US8856024Oct 25, 2011Oct 7, 2014Cubic CorporationDetermining companion and joint cards in transit
US8942677Sep 11, 2012Jan 27, 2015Cubic CorporationTransit account management with mobile device messaging
US8977251 *Jan 31, 2011Mar 10, 2015Bank Of America CorporationTransferring content to a mobile device
US8991699Sep 8, 2010Mar 31, 2015Cubic CorporationAssociation of contactless payment card primary account number
US9038129Jan 18, 2013May 19, 2015Proxicom Wireless, LlcEnforcing policies in wireless communication using exchanged identities
US9135612Apr 17, 2012Sep 15, 2015Proctor Consulting, LLCProximity detection, virtual detection, or location based triggering of the exchange of value and information
US9161164Aug 29, 2014Oct 13, 2015Proxicom Wireless, LlcExchanging identifiers between wireless communication to determine further information to be exchanged or further services to be provided
US9208337 *Sep 22, 2010Dec 8, 2015Denise G. TayloeSystems, methods, and software applications for providing and identity and age-appropriate verification registry
US20090271315 *Oct 29, 2009Ayman HammadPortable device including alterable indicator
US20100062746 *Mar 11, 2010Proctor Jr James ArthurProtocol for anonymous wireless communication
US20100063889 *Feb 3, 2009Mar 11, 2010Proctor Jr James ArthurVisual identification information used as confirmation in a wireless communication
US20100131347 *Oct 2, 2009May 27, 2010Research In Motion LimitedElectronic payment system using mobile wireless communications device and associated methods
US20100179891 *Jul 15, 2010Visa U.S.A. Inc.Non-financial transactions in a financial transaction network
US20100258625 *Oct 14, 2010Intersections Inc.Dynamic Card Verification Values and Credit Transactions
US20110072039 *Sep 22, 2010Mar 24, 2011Tayloe Denise GSystems, methods, and software applications for providing an identity and age-appropriate verification registry
US20110145148 *Jun 16, 2011Ayman HammadMerchant alerts incorporating receipt data
US20110166914 *Jul 7, 2011Cubic CorporationReloadable prepaid card distribution, reload, and registration in transit
US20110166936 *Jul 9, 2010Jul 7, 2011Cubic CorporationPredictive techniques in transit alerting
US20110225089 *Sep 15, 2011Ayman HammadSystem and method including security parameters used for generation of verification value
US20110225090 *Sep 15, 2011Ayman HammadSystem and method including customized linkage rules in payment transactions
US20110225094 *Sep 15, 2011Ayman HammadSystem and method including dynamic verification value
US20110246363 *Oct 6, 2011Ebay Inc.Two device authentication
US20120196586 *Aug 2, 2012Bank Of America CorporationTransferring content to a mobile device
US20130140359 *Aug 12, 2011Jun 6, 2013Alibaba Group Holding LimitedMethod and System of Sending Information Based on a User Card
DE102011077770A1 *Jun 17, 2011Dec 20, 2012WR Information Management GmbHPayment system for cashless payment of goods and services between payer and payee, has online management portal through which payer and payee are authenticated after transmitting transaction record along with record of payee to portal
Classifications
U.S. Classification705/1.1, 726/20, 455/550.1
International ClassificationH04L9/32, H04M1/00, G06Q20/00
Cooperative ClassificationG06Q20/322, G06Q20/04, G06Q30/0233, G06Q20/32, G06Q20/105, G06Q20/40, G06Q20/341
European ClassificationG06Q20/32, G06Q20/04, G06Q20/322, G06Q20/105, G06Q20/40, G06Q30/0233, G06Q20/341
Legal Events
DateCodeEventDescription
Apr 29, 2009ASAssignment
Owner name: VISA U.S.A. INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HAMMAD, AYMAN;REEL/FRAME:022615/0982
Effective date: 20090428
Aug 30, 2011ASAssignment
Owner name: VISA U.S.A. INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MAW, BRIAN;REEL/FRAME:026831/0673
Effective date: 20110201