EP3055818A1 - System and method for dynamic temporary payment authorization in a portable communication device - Google Patents
System and method for dynamic temporary payment authorization in a portable communication deviceInfo
- Publication number
- EP3055818A1 EP3055818A1 EP14869040.7A EP14869040A EP3055818A1 EP 3055818 A1 EP3055818 A1 EP 3055818A1 EP 14869040 A EP14869040 A EP 14869040A EP 3055818 A1 EP3055818 A1 EP 3055818A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- payment
- portable communication
- communication device
- merchant
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4012—Verifying personal identification numbers [PIN]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/20—Point-of-sale [POS] network systems
- G06Q20/204—Point-of-sale [POS] network systems comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/22—Payment schemes or models
- G06Q20/227—Payment schemes or models characterised in that multiple accounts are available, e.g. to the payer
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/322—Aspects of commerce using mobile devices [M-devices]
- G06Q20/3224—Transactions dependent on location of M-devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/322—Aspects of commerce using mobile devices [M-devices]
- G06Q20/3227—Aspects of commerce using mobile devices [M-devices] using secure elements embedded in M-devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/322—Aspects of commerce using mobile devices [M-devices]
- G06Q20/3229—Use of the SIM of a M-device as secure element
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/327—Short range or proximity payments by means of M-devices
- G06Q20/3278—RFID or NFC payments by means of M-devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
- G06Q20/363—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes with the personal data of a user
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3821—Electronic credentials
- G06Q20/38215—Use of certificates or encrypted proofs of transaction rights
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3823—Payment protocols; Details thereof insuring higher security of transaction combining multiple encryption tools for a transaction
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3825—Use of electronic signatures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/385—Payment protocols; Details thereof using an alias or single-use codes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/387—Payment using discounts or coupons
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4016—Transaction verification involving fraud or risk level assessment in transaction processing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/50—Secure pairing of devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
- H04W4/023—Services making use of location information using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
Definitions
- the present invention relates generally to the use of secure data to complete a wireless transaction, and more particularly to a system and method for processing a temporary electronic payment credential for use with a portable communication device.
- RFID which stands for radio-frequency
- identification uses electromagnetic waves to exchange data between a terminal and some object for the purpose of identification. More recently, companies have been trying to use RFIDs supported by cellular telephones to implement an electronic payment product (i.e. credit and/or debit card). However, basic RFID technology raises a number of security concerns that have prompted modifications of the basic technology. Still, widespread adoption of RFID as a mechanism for electronic payments has been slow.
- NFC Near Field Communication
- ISO/IEC 18092 ISO/IEC 18092
- modulation schemes coding
- transfer speeds RF interface
- a deliberate physical gesture e.g. waving the mobile device in front of the reader device
- NFC provides better security for financial transactions and access control.
- Other short distance communication protocols are known and may gain acceptance for use in supporting financial transactions and access control.
- NFC devices are already being used to make payments at some point of sale devices. But there are many mobile devices do not have the Secure Element hardware typically used to store contactless payment credentials securely. Accordingly, the present invention seeks to provide a solution to enable any smartphone to make highly secure electronic payments at merchants that accept contactless electronic payments with existing point-of-sale equipment.
- Another problem is the myriad of credential types and communications protocols associated with the various different point of sale terminals available. So, for instance, one merchant may rely on barcode scanning while others may rely on contactless NFC or Bluetooth Low-Energy. And the radio protocol necessary to successfully communicate wirelessly with an IBM point of sale terminal may be very different from the radio protocol necessary to communication with an NCR terminal. Accordingly, some embodiments of the present invention seek to use geo-location data (where available) to try to predetermine the likely credential type, point of sale redemption method, terminal device type, and/or communication protocols present in the retail establishment co-located with the portable communication device.
- the present invention also seeks to provide one or more solutions to the foregoing opportunities and related problems as would be understood by those of ordinary skill in the art having the present specification before them.
- FIG. 1A illustrates an end user attempting to use her portable communication device to conduct a secure payment transaction at a point of sale.
- FIG. IB illustrates the operable interconnections between the end user's smartphone (i.e. portable communication device) and various subsystems, including the system management back end.
- FIG. 2 is a block diagram illustrating some of the logical blocks within a portable communication device that may be relevant to the present system.
- FIG. 4 is a block diagram illustrating the information flow between a portable communication device and the remainder of the payment ecosystem in relation to the payment process illustrated in FIGS. 3 A and 3B.
- FIGS. 5, 6, and 6A are illustrations of an exemplary wallet user interface that may be deployed on a representative portable communication device.
- FIGS. 7 A, and 7B are illustrations of two potential embodiments of one-time payment credentials generated by an exemplary wallet user interface on a representative portable communication device.
- FIG. 8A is a block diagram illustrating some of the logical blocks within a portable communication device that may be relevant to the present system
- FIG. 8B is a block diagram illustrating further detail of the "one-time payment wallet" block of FIG. 8A that may be relevant to the present system.
- FIGS. 9 A and 9B together illustrate one potential embodiment of a user interface that may be implemented on the illustrative smart phone further illustrating the flexibility of the one-time credential functionality coupled with a federated wallet.
- FIGS. 9C and 9D illustrate another potential embodiment of a user interface that may be implemented on a portable communication device further illustrating the ability of an issuer to communicate directly with a user to obtain information that is often so sensitive (e.g. "Know your Customer” and CVV) entities prefer not to share the data.
- information that is often so sensitive (e.g. "Know your Customer” and CVV) entities prefer not to share the data.
- FIG. 10 is a block diagram of one potential implementation of a system underlying the grant of permission for the one-time payment app to view, select and/or change secure data stored in the payment subsystem.
- FIG. 11 A is a block diagram illustrating the information flow between a portable communication device and the remainder of the payment ecosystem in relation to an
- FIG. 1 IB illustrates communication flow for obtaining a temporary credential token in one potential embodiment of a process.
- FIG. 12 illustrates a payment communication flow using a temporary credential token in one potential embodiment of a process.
- FIG. 13 illustrates an encryption mechanism that may be used in one potential embodiment of a process of obtaining and using a temporary electronic credential.
- the present invention provides a system and method that can be utilized with a variety of different portable communication devices, including but not limited to PDA's, cellular phones, smart phones, laptops, tablet computers, and other mobile devices that preferably include cellular voice and data service as well as preferably access to consumer downloadable applications.
- portable communication device could be an iPhone, Motorola RAZR or DROID; however, the present invention is preferably platform and device independent.
- the portable communication device technology platform may be Microsoft Windows Mobile, Microsoft Windows Phone 7, Palm OS, RIM Blackberry OS, Apple OS, Android OS, Symbian, Java or any other technology platform.
- the present invention has been generally described in accordance with features and interfaces that are optimized for a smart phone utilizing a generalized platform, although one skilled in the art would understand that all such features and interfaces may also be used and adapted for any other platform and/or device.
- the portable communication device preferably includes one or more short proximity electromagnetic communication devices, such as an NFC, RFID, or Bluetooth transceiver. It is presently preferred to use an NFC baseband that is compliant with NFC IP 1 international standards (ISO/IEC 18092) and compliant to industry protocol standards such as those published by the NFC Forum (www.nfc-forum.org), which provide standard functions like peer-to-peer data exchange, reader-writer mode (i.e. harvesting of information from NFC tags), and contactless card emulation (per the NFC IP 1 and ISO/IEC 14443 standards) when paired with a secure element on the portable communication device and presented in front of a
- NFC IP 1 international standards ISO/IEC 18092
- industry protocol standards such as those published by the NFC Forum (www.nfc-forum.org)
- reader-writer mode i.e. harvesting of information from NFC tags
- contactless card emulation per the NFC IP 1 and ISO/IEC 14443 standards
- the NFC IP 1 standards are simply the presently preferred example, which could be exported - in whole or in part - for use in association with any other proximity communication standard.
- the portable communication device include an RFID antenna or an NFC antenna (conformed to NFC IP 1 and ISO 14443 standards and to other payment card industry standards such as those promulgated by EMV Co) to enable near field communications.
- NFC as well as RFID communications may be accomplished using various non-conforming antennae and coil designs, over potentially even shorter ranges albeit with varying communication reliability and with other potential interoperability problems.
- the portable communication device also includes a network interface to establish and manage wireless communications with a mobile network operator.
- the network interface uses one or more communication protocols and technologies including, but not limited to, global system for mobile communication (GSM), 3G, 4G, code division multiple access (CDMA), time division multiple access (TDMA), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), user datagram protocol (UDP), transmission control protocol/Internet protocol (TCP/IP), SMS, general packet radio service (GPRS), WAP, ultra wide band (UWB), IEEE 802.11 (WiFi), IEEE 802.16 Worldwide Interoperability for Microwave Access (WiMax), SIP/RTP, or any of a variety of other wireless communication protocols to communicate with the mobile network of a mobile network operator.
- GSM global system for mobile communication
- 3G, 4G code division multiple access
- TDMA time division multiple access
- TD-SCDMA Time Division Synchronous Code Division Multiple Access
- UDP user datagram protocol
- TCP/IP transmission control protocol/Internet protocol
- the mobile network interface may include as a transceiver, transceiving device, or network interface card (NIC). It is contemplated that the mobile network interface and short proximity electromagnetic communication device could be implemented in a hybrid or combination transceiver or transceiving device, as would be understood in the art by those having the present specification, figures, and claims before them.
- NIC network interface card
- the portable communication device further preferably includes a location transceiver that can determine the physical coordinates of device on the surface of the Earth typically as a function of its latitude, longitude and altitude.
- This location transceiver preferably uses GPS technology, so it may be referred to herein as a GPS transceiver; however, it should be understood that the location transceiver can additionally (or alternatively) employ other geo- positioning mechanisms, including, but not limited to, triangulation, assisted GPS (AGPS), GLONASS, E-OTD, CI, SAI, ETA, BSS or the like, to determine the physical location of the portable communication device on the surface of the Earth.
- Altitude may be determined separately by other means or it may be part of the GPS function.
- the location of the mobile device may be inferred or refined by the collection of network identities (e.g. detectable WiFi SSIDs, discoverable Bluetooth beacon IDs, access point MAC addresses).
- network identities e.g. detectable WiFi SSIDs, discoverable Bluetooth beacon IDs, access point MAC addresses.
- the portable communication device further includes a user interface that provides some means for the consumer to receive information as well as to input information or otherwise respond to the received information.
- this user interface may include a microphone, an audio speaker, a haptic interface, a graphical display, and a keypad, keyboard, pointing device and/or touch screen.
- the portable communication device will also include a microprocessor and mass memory.
- the mass memory may include ROM, Flash memory, RAM, non-volatile RAM, as well as one or more removable memory cards.
- the mass memory provides storage for computer readable instructions and other data, including a basic input/output system ("BIOS") and an operating system for controlling the operation of the portable communication device.
- BIOS basic input/output system
- the portable communication device will also include a device identification memory dedicated to identify the device, such as an electronic serial number (ESN), Mobile Equipment ID (MEID), International Mobile Equipment Identifier (IMEI).
- the portable communication device may also include a subscriber identity module, such as a SIM card or Universal Integrated Circuit Card (UICC) with a SIM application present and configured for network access.
- SIM cards contain a unique serial number, identity of the issuing operator, an internationally unique number of the mobile user (IMSI), security authentication and ciphering information, temporary information related to the local network, a list of the services the user has access to and two passwords (PIN for usual use and PUK for unlocking).
- IMSI internationally unique number of the mobile user
- PIN personal information provider
- Portable communication devices may have two subsystems: (1) a "wireless subsystem” that enables communication and other data applications as has become commonplace with users of cellular telephones today, and (2) the "secure transactional subsystem” which may also be known as the "payment subsystem”.
- the secure transactional subsystem would include a secure element and associated device software for communication to management and provisioning systems as well as the customer facing interface for use and management of secure data stored in the secure element. It is contemplated that this secure transactional subsystem will preferably include a Secure Element, similar (if not identical) to that described as part of the Global Platform 2.1.X, 2.2, or 2.2.X (www.globalplatform.org).
- the secure element has been implemented as a specialized, separate physical memory used for industry common practice of storing payment card track data used with industry common point of sale; additionally, other secure credentials that can be stored in the secure element include employment badge credentials (enterprise access controls), hotel and other card-based access systems and transit credentials.
- Some portable communication devices may not have a secure transaction subsystem and particularly not have a secure element.
- Each of the portable communications devices is connected to at least one mobile network operator.
- the mobile network operator generally provides physical infrastructure that supports the wireless communication services, data applications and the secure transactional subsystem via a plurality of cell towers that communicate with a plurality of portable
- the cell towers may be in operable communication with the logical network of the mobile network operator, POTS, and the Internet to convey the communications and data within the mobile network operator's own logical network as well as to external networks including those of other mobile network operators.
- the mobile network operators generally provide support for one or more
- GSM global system for mobile communication
- 3G 3G
- 4G code division multiple access
- TDMA time division multiple access
- UDP user datagram protocol
- TCP/IP transmission control protocol/Internet protocol
- SMS general packet radio service
- WAP WAP
- UWB ultra wide band
- WiMax IEEE 802.16 Worldwide Interoperability for Microwave Access
- SIP RTP SIP RTP, or any of a variety of other wide area or local area wireless communication protocols to communicate with the portable communication devices.
- Standard at merchants today is an Internet Protocol connected payment system that allows for transaction processing of debit, credit, prepay and gift products of banks and merchant service providers.
- a magnetic stripe enabled card at the magnetic reader of a Point of Sale (or Point of Purchase) Terminal
- the card data is transferred to the point of sale equipment and used to confirm funds by the issuing bank.
- This point of sale equipment has begun to include contactless card readers as accessories that allow for the payment card data to be presented over an RF interface, in lieu of the magnetic reader.
- the data is transferred to the reader through the RF interface by the ISO/IEC 14443 standard and proprietary payment applications like PayPass and Paywave, which transmit the contactless card data from a card or a mobile device that includes a Payment Subsystem.
- a retailer's point of sale device 75 may be connected to a merchant payment network via a wireless or wired connection.
- This point of sale network may include the Internet in addition to local area networks (LANs), wide area networks (WANs), direct connections, such as through a universal serial bus (USB) port, other forms of computer-readable media, or any combination thereof.
- LANs local area networks
- WANs wide area networks
- USB universal serial bus
- a router acts as a link between LANs, enabling messages to be sent from one to another.
- communication links within LANs typically include twisted wire pair or coaxial cable
- communication links between networks may utilize analog telephone lines, full or fractional dedicated digital lines including Tl, T2, T3, and T4, Integrated Services Digital Networks (ISDNs), Digital Subscriber Lines (DSLs), wireless links including satellite links, or other communications links known to those skilled in the art.
- ISDNs Integrated Services Digital Networks
- DSLs Digital Subscriber Lines
- remote computers and other related electronic devices could be remotely connected to either LANs or WANs via a modem and temporary telephone link.
- the point of sale network may utilize any communication method that allows information to travel between the point of sale devices and financial services providers for the purpose of validating, authorizing and ultimately capturing financial transactions at the point of sale for payment via the same financial services providers.
- the system includes a system management back end.
- the system management back end 300 is connected to the retail subsystem (see point of sale device 75), the secure transactional subsystem (made up of one or more financial service providers) 310, and to a plurality of portable communication devices 50 via the infrastructure of at least one mobile network operator.
- the system management back end 300 comprises a server operably communicating with one or more client devices.
- the server is also in operable communication with the retailer subsystem 75, secure transactional subsystem 310, and one or more portable communication devices 50. Any type of voice channel may be used in association with the present invention, including but not limited to VoIP.
- the server of the system management back end 300 may comprise one or more general-purpose computers that implement the procedures and functions needed to run the system back office in serial or in parallel on the same computer or across a local or wide area network distributed on a plurality of computers and may even be hosted by a third-party service provider on hardware connected via the Internet (a service hosting scheme known as "in the cloud").
- the computer(s) comprising the server may be controlled by Linux, Windows®, Windows CE, Unix, or a Java® based operating system, to name a few widely used server technology platforms or it may be controlled by proprietary programming.
- the system management back end server is operably associated with mass memory that stores program code and data. Data may include one or more databases, text, spreadsheet, folder, file, or the like, that may be configured to maintain and store a knowledge base, user identifiers (telephone number, email/IM address, billing information, or the like).
- the system management back end server may support a case management system to provide call traffic connectivity and distribution across the client computers in the customer care center.
- a case management system to provide call traffic connectivity and distribution across the client computers in the customer care center.
- VoIP voice channel connectivity the case
- the system management back end server also supports issuing engine 2010, user unique identification database 2011, merchant-geolocation collation database 2012, and predictive transaction module 2015. These elements will be described later in the specification.
- Each client computer associated with the system management back end server has a network interface device, graphical user interface, and voice communication capabilities that match the voice channel(s) supported by the client care center server, such as VoIP.
- Each client computer can request status of both the cellular and secure transactional subsystems of a portable communication device. This status may include the contents of the soft memory and core performance of portable communication device, the NFC components: baseband, NFC antenna, secure element status and identification.
- each portable communication device 50 may contain onetime payment wallet 160, payment libraries 110, an NFC (or RF) Baseband, a payment subsystem 150 (i.e. secure data store 115 and secure element 120), and diagnostic agent 170.
- One-time payment wallet 160 is an application that enables any portable communication device to request and emulate credentials (e.g., card, coupon, access control and ticket data) in association with NFC/RF Baseband that are downloaded to the device 50 (preferably into payment subsystem 150) for temporary use.
- the application may also be implemented on legacy feature phones (non-smartphones) using WAP, J2ME RTE, and/or SMS channel in lieu of smartphone application.
- the credentials are most preferably NFC based, but they may be transacted by means of RFID or Bluetooth transmission, or displayed as 2-D matrix codes, bar codes or Arabic numerals.
- the payment libraries 110 are used by one-time payment wallet 160 to manage
- OTA over-the-air
- the OTA data communications will be encrypted in some manner and an encryption key will be deployed in a card service module that is operably associated with the portable
- card services module is operably coupled to one-time payment wallet 160 (deployed as a third party application as described below) and to the payment subsystem 150.
- Card services module generally enforces access control to the data stored in the payment subsystem 150 and controls the function(s) each application is allowed to conduct with the payment subsystem 150.
- card services module verifies the author/issuer of each third party application in use on the portable communications device to access the payment subsystem (as generally described below).
- the payment subsystem 150 may be used to store credentials such as the temporary one-time payment card in addition to other payment card(s), coupon, access control and ticket data (e.g., transportation ticket data, concert ticket data, etc.).
- the secure data store 115 would provide secured storage on the portable communication device 50.
- Various levels of security may be provided depending upon the nature of the data intended for storage in secure data store 115.
- secure data store 115 may simply be password-protected at the operating system level of device 50.
- the password may be a simple alphanumeric code or a hexadecimal representation of a binary code that is stored somewhere on the device 50.
- the data in secure data store 115 is preferably encrypted. More likely, however, the secure data store 115 will be set up as a virtual secure element in the manner disclosed in the co-pending patent application (owned by the assignee of the present application) entitled "System and Method for Providing A Virtual Secure Element on a Portable Communication Device," U.S. Patent Application No. 13/279,147, filed on October 21, 2011 and hereby incorporated by reference.
- the present invention enables any portable communication device (including those with NFC capability but without a Secure Element and devices without NFC capability) to make highly secure electronic payments at merchants that accept either contactless payments or barcode electronic payments via their existing point-of-sale equipment.
- the consumer In order to use the system for a dynamic temporary (e.g. one-time) payment to a retailer, the consumer will have downloaded a dynamic temporary (e.g. one-time) payment wallet application and have at least one existing account with a specified bank. The consumer should also have registered the at least one account with payment issuer 310 (which may also be the specified bank). In addition, the consumer should also have a mobile data service for their smart phone (or portable communication device 50).
- the dynamic temporary (e.g. One-time) payment wallet 160 may remove some of the complexity involved in the storage, maintenance and use of credentials because of the temporary nature of the credentials and its combination with geo-location confirmation.
- Payment Wallet 160 may include some of the complexity involved in the storage, maintenance and use of credentials because of the temporary nature of the credentials and its combination with geo-location confirmation.
- a. wallet management e.g., set, reset or enable wallet passcodes; get URL of OTA server; over-the-air registry provisioning; set payment timing; increase payment timing; set default card; list issuers, memory audit; determine SE for storage of credential; update wallet status
- credential management e.g., add credential; view credential detail; delete
- Secure Element Management of physical and/or virtual Secure Element(s) for use by Payment Wallet 160 (e.g., get credential; update credential; update meta data; delete credential; wallet lock/unlock; SE lock/unlock, SE initialize/wipe/reset) as disclosed by Applicant's co-pending application serial number 13/279,147 entitled "System and Method for Providing a Virtual Secure Element on a Portable Communication Device," filed on October 21, 2011, which is hereby incorporated by reference.
- this SE management may use various techniques to protect the dynamic credential received, including the encryption of standard memory under a user password.
- FIGS. 3A-3B together illustrate one potential embodiment (with various potential alternatives) for a process for obtaining and using a one-time (i.e. dynamic temporary) payment credential using the "one-time" payment wallet 160.
- the consumer may enter a physical retail store with their smartphone (i.e. portable communication device 50) and go about their shopping experience as normal.
- the one-time payment wallet 160 downloaded on their smartphone 50, when the consumer is ready to check out of the physical retail store, the consumer may use their smart phone to pay even with a legacy system by opening a solution-enabled smartphone application.
- the consumer approaches the point-of-sale 75, opens the one-time payment wallet 160 on smartphone 50, enters the consumer's
- the one- time payment wallet 160 sends the consumer's passcode and geo-location coordinates (as generated by the location identification service 165, FIG. 2) to the issuing engine 2010 (FIG. 4).
- one-time payment wallet 160 may also provide an ability for the consumer to communicate the estimated amount of the upcoming payment to the issuing engine 2010 prior to generation of the temporary payment card information. By incorporating information regarding the estimated amount of the one-time payment into the confirmation process, additional security for the one-time code may be provided.
- the issuing engine 2010 verifies the passcode
- Receipt of the correct passcode indicates to the system that the consumer will be making a payment within a short predetermined period of time (on the order of a few minutes, which could be extended in certain circumstances).
- the issuing engine 2010 may also verify the digital signature of the portable communication device 50 that transmitted the passcode.
- a digital signature is comprised of at least a portion of one of more of the numbers identified in paragraph [0034] stored in the device identification memory of each portable communication device 50.
- the issuing engine 2010 uses the geo location coordinates received from the portable communication device 50 to determine the likely merchant and looks up the merchant's point-of-sale details in a database operably associated with the issuing engine 2010 (e.g., the merchant-geolocation collection database 2012). In particular, based on the geo-location information received, the issuing engine 2010 performs a database query to determine which contactless point of sale terminal is installed (or likely to be installed) at the consumer's location. In a preferred embodiment, the portable communication device 50 may also display a list of the next most likely retail stores (e.g. the next top five) where the portable communication device 50 may be located (see, e.g. FIG. 6A).
- a database operably associated with the issuing engine 2010 e.g., the merchant-geolocation collection database 2012.
- the issuing engine 2010 performs a database query to determine which contactless point of sale terminal is installed (or likely to be installed) at the consumer's location.
- the portable communication device 50 may also display a list of
- the card services module of the portable communication device 50 may lookup in a database or otherwise infer the merchant or facility at which the consumer is located and configures the payment system 150 with the data formats and other contactless point of sale or access data specific to this location and/or merchant such that the device 50 is supported or optimal presentation of card, coupon, ticket or access control emulation.
- the system may also identify to the consumer new card products available for that geo-location that the consumer does not already have loaded in payment libraries 110. In some embodiment, the system may load needed libraries.
- the issuing engine 2010 includes a database (e.g., the merchant/facility geolocation collection database 2012) of electronic-payment accepting merchants and supported access-controlled facilities, which may include the merchant location, facility identity, merchant identification number used in electronic payments, the payment schemes accepted by each merchant location, and the capabilities of each merchant location's point of sale or access control equipment capabilities. (See Table 1 below).
- a database e.g., the merchant/facility geolocation collection database 2012
- the merchant/facility geolocation collection database 2012 may be included within, part of or associated with the portable communication device 50, the issuer 310 or separately hosted.
- the merchant location may further include the merchant's altitude.
- merchant/facility geolocation may be represented using map coordinates but could effectively also be represented using street address or proprietary coordinates relative to a surveyed baseline or point.
- the altitude of the merchant/facility may be represented as a physical length measure or distance measure (e.g. feet, meters) with reference to a recognized international map datum (e.g. WGS84) but could also effectively be represented in relative terms such as height above ground level, floor number, or proprietary coordinates relative to a surveyed height reference.
- the issuing engine 2010 then generates the one-time use temporary payment card and transmits the temporary payment card data and identity of the likely merchant to the portable communication device 50 over-the-air.
- This temporary payment card information may be formatted in real time using existing standards and practices of the legacy electronic payment industry, including personal account number, issuer identification number, ISO/IEC 7812 (relating to the identification of issuers using an issuer identification number (UN) to operate in an international, inter-industry, and /or intra-industry interchange), ISO/IEC 7813 (relating to the data structure and content of magnetic stripe tracks used to initiate financial transactions), and ISO 8583 formatting (which is a business messaging protocol, based on a proprietary standard).
- the one-time payment wallet 160 formats the temporary payment card based on the capabilities of the portable communication device 50 as well as the capabilities of the merchant's point-of-sale equipment 75.
- the temporary payment card information may also be formatted in multiple formats to provide the consumer with options that may be presented to the merchant cashier.
- FIGS. 7A and 7B illustrate two of the possible types of one-time payment codes that can be transmitted to the portable communication device 50.
- FIG. 7A depicts the one-time payment code as a 1-D bar code. As would be understood by those of ordinary skill in the art this bar code could be a 2-D matrix code or stacked linear barcode (e.g. QR code, Datamatrix, EZCode, PDF417).
- FIG. 7B depicts the one-time payment code as a numeric code, which may be 16 digits as shown or a different length as desired.
- One format that the temporary payment card information may be rendered on the smartphone display is an ISO/IEC 7813 compliant number (i.e., PAN) that the clerk at the merchant enters by hand into the merchant point-of-sale.
- Another format that the temporary payment card data may be rendered on the smartphone display in barcode (ISO/IEC 15426-1), 2- D barcode (ISO/IEC 15426-2), QR code (ISO/IEC 18004:2006), or other such similar methods that transmit ASCII, alphanumeric, or numeric data, then captured by the optical scanner of the merchant's point of sale.
- Yet another format that the temporary payment card data may be rendered using NFC Peer-to-Peer mode (ISO/IEC 18092), NFC Tag Emulation (NDEF,
- the temporary payment card data may be rendered using sonic or hypersonic audio carrier generated by the portable device speaker and received by an accessory appliance at the merchant point of sale terminal.
- the activated temporary payment card data expires after a short predetermined period of time, such as two (2) minutes to provide further security. This time could be extended as long as the issuer is willing. It is believed that less than 30 minutes, or even less than 20 minutes or even 10 minutes would be preferred. Other expiration times can be used and/or programmed as desired.
- the portable communication device 50 receives the temporary credential data, likely merchant, and emulation information from the issuing engine 2010. In a preferred embodiment, the portable communication device 50 confirms the likely merchant was correctly selected from database 2012. In one approach illustrated in association with FIG. 6, the portable communication device asks the user to the confirm the location. In the illustrated example, the user interface asks whether the location is "Grocery Land"? As the consumer is shown in FIG. 1A standing in Grocery Land, the consumer should select the "yes" button on FIG. 6. If the system has selected the wrong retailer, the system may provide alternatives for ascertaining the correct retailer. For example, FIG.
- 6A depicts the provision of a list of potential merchants close to the consumers' proximity in an example where the one-time credential was requested from within what the issuing engine 2010 recognized as a mall (or other high-density grouping of merchants).
- the list of nearby merchants need not be limited to those merchants within a single mall. Alternatives may be selected from other retailers that were geographically close to the geo-location received by the server.
- the alternatives may be presented to the end user in the form of a pull-down menu or list, as an example, as a map overlay showing geographical location of each retailer, as a floor plan overly, such as used in a mall, plaza, or building directory, or other situationally relevant forms.
- the confirmation of the likely merchant may be received by issuing engine 2010. If the likely merchant was identified incorrectly, then the issuing engine may issue new emulation information to the portable communication device 50. Once the likely merchant is known, the predictive transaction module 2015 of issuing engine 2010 transmits the ID for that likely merchant, the unique user ID associated with portable communication device 50, the one-time use token generated for the transaction, and the expiration time to the validation mapping gateway 2020.
- the validation mapping gateway 2020 may be physically hosted by a bank, by an issuer 310, or by a payment processor network and may be deployed as either a service or as a sub- system installed and integrated at existing transaction processors, card schemes, financial institutions, and other entities.
- the received data is stored in a database associated with the validation mapping gateway.
- the temporary data may be associated with the legacy card data previously associated with the unique user ID. To the extent such associations exist, mapping legacy card-to-unique user ID, it may be created by the issuers 310 or even by the consumer in an electronic transaction directly between the portable communication device 50 and the validation mapping gateway 2020 orchestrated by the system management back end 300.
- the predictive transaction module 2015 send the data to the validation mapping gateway 2020 at substantially the same time one-time use credential information is being transmitted to the portable communication device 50.
- the validation mapping gateway 2020 can anticipate the consumer transaction from the merchant POS 75 via the merchant payment network.
- the Validation mapping gateway 2020 may use the time between receiving data from the predictive transaction module 2015 and receipt of the transaction from the retailer point-of-sale 75 to bring stored data out of the large database and into a memory that provides for quicker access (in comparison to the access time from a large database) and comparison between the stored data and the data received from the merchant payment network.
- the addition of this additional verification step in the validation mapping gateway 2020 will create less latency than may have otherwise been caused by the need to locate and retrieve the data for this comparison after receiving a transaction from the POS 75.
- the consumer may then tap or otherwise activate the smart phone 50 on the NFC peer-to-peer-enabled point of sale device 75, which causes the portable communication device to emulate the credential with the one-time payment code using the emulation protocol provided by the server. It being understood that the code may be visually "emulated" on the screen of the portable communication device 50. Because the temporary payment card data may be provided in legacy formats, the temporary payment card data may be accepted by existing merchant point-of-sale equipment 75.
- the point of sale device 75 then processes the temporary payment card data through normal merchant payment network as if it were a standard credit or debit credential. However, because the temporary payment card data uses Issuer Identification Numbers
- the data will be routed to the validation mapping gateway 2020 via the merchant payment network. If the data is received by the validation mapping gateway 2020 prior to the expiration of the expiration time for the temporary credential and from the anticipated likely merchant, then the validation mapping gateway 2020 may authorize the transaction. The validation mapping gateway 2020 may also compare the method by which the temporary payment card data was entered into the merchant point-of-sale device 75 (existing IS08583 specified field) with the method the temporary card data was provisioned for intended use to the mobile phone (e.g. Numeric code, barcode, NFC).
- the validation mapping gateway may return a confirmation to the merchant with authorization code via the merchant payment network or facility access network.
- the merchant point-of-sale 75 receives the authorization (i.e.
- validation mapping gateway 2020 substitutes legacy card payment data in the transaction data, which is then passed onto the issuer authorization systems 310 along with standard POS transaction information (e.g. merchant ID, and transaction amount) and - in some embodiments— an indication that the transaction used a verified one-time use credential (to show an added measure of security).
- the issuer 310 will review the legacy card data and transaction information toward determining whether to authorize the transaction in a manner generally known in the art perhaps with the information that the transaction had the added security noted above.
- the issuer authorization is sent back to the merchant point-of-sale 75 via the normal existing processing channel.
- This one-time (or temporary)-use credential solution can be used for many different types of credential validation scenarios including: credit card and debit card payments, gift card, loyalty card, coupons and offers, access control, transit fare, event ticketing, and any other environment where a consumer presents a credential for validation in a physical environment.
- the user interface may be provided by wallet user interface and the over-the-air provisioning and management of and access to the secure payment subsystem is supported by the functionality of the card services module.
- the card services module facilitates over-the-air provisioning, secure element management, and direct key exchange between the card services module on the user's mobile device 50 and the appropriate issuer server (for onetime payment wallet 160 that would be issuing engine 2010) in an encrypted fashion as was previously known in the art.
- the one-time payment wallet 160 may be deployed as one of many trusted third party applications 200.
- the card services module verifies the trusted status of any application 200 before that application is allowed access to the secure element 120, , (or secure data store 115 and even preferably the meta data repository which stores, among other things, card image data and any embossed card data) on the portable communication device 50 to view, select and/or change secure data stored in the payment subsystem 150.
- This verification may be accomplished by accessing a local authorization database of permitted or trusted applications.
- the local authorization database cooperates with a remote authorization database associated with one or more servers associated with system management back end 300.
- Applications may be identified using various means, including technology platform facilities such as strong assembly references, hash coding of the application's executable code or load file, an app developer's API key or oAuth token, and other means known to those of ordinary skill in the art of smartphone application development.
- FIG. 10 is a block diagram of one potential implementation of one potential combination local and remote authorization databases to enhance security of the card services module, secure element 120, and payment subsystem 150.
- a User A/C Registry (or User Account Registry) may be associated with the server (or otherwise deployed in the cloud).
- the User A/C Registry may store the identification of the secure element 120 disposed in each user's portable device 50. Entries in the User Account Registry may be added for each user at any point in the process.
- the "Issuer Registry” database is a database of approved Issuers.
- the Issuer ID is unique for each type of credential.
- each credential type would have its own Issuer ID (e.g. I-BofA-II).
- the Issuer ID as between multiple types of credentials would have some common elements, so as to indicate that the credentials are at least related (e.g. I-BofA-I). In this way applications from same the issuer can share data with the other application of the same "extended" issuer.
- card services module can be simplified by requiring even the wallet user interface (which "ships with the system") to have an Issuer ID (and as well as an Application ID and Compile token).
- the "Application Registry” is a database of applications (mostly third party) that have been pre-approved by an operating system provider. Like the User A/C Registry, the "Application Registry” and “Issuer Registry” database are maintained on the server side (or otherwise hosted by a third-party Internet-connected facility) in operable association with the one-time payment application. As would be understood by those of ordinary skill in the art having the present specification before them, the various registries may be implemented in separate databases or one unified database. At initiation of a wallet 160 and preferably at substantially regular time- intervals thereafter (e.g., daily), the data stored in the Application Registry of the one-time payment wallet 160 is distributed to devices with the wallet to be stored locally.
- substantially regular time- intervals thereafter e.g., daily
- the Application Registry may include, among other information, an Application ID ("App ID”), an Issuer ID, and a Compile ID or token.
- the Compile ID is a global constant generated for each application by one or more processes associated with one-time payment wallet during the qualification process for the particular application. After it is generated by a particular card services module on a unique device 50, the Compile token is included or otherwise associated with the application.
- This Compile token is preferably generated by a pseudo-random number generator local to the device that uses a predetermined seed, such as the Application ID, Compile ID, Issuer ID or some combination thereof.
- the Compile ID (a digital token) and Application ID (a digital identifier) associated with the third party application may be matched against the Compile ID and Application ID pairs stored in the Card Services Registry stored on the device 50 (see Fig. 10).
- the same Compile and Application ID pairs are transmitted to other devices 50 associated with the system, as well.
- a Secret Token ID is preferably generated on the device 50 by a pseudo-random number generator (such as the one associated with the Secure Element 120 and then stored in association with the Compile ID/ Application ID pair in the Card Services Registry on the device 50.
- the Compile ID may be pre-selected and used to seed the random number generator. It should be understood that one or more pieces of other
- the Card Services Registry is preferably stored in secure memory (rather than the secure element 120 because secure element 120 has limited real estate) and the Card Services Registry is preferably further encrypted using standard encryption techniques.
- the Secret Token ID is also embedded in or otherwise associated with the application 200 on the device 50 in place of the Compile ID that was distributed with the application.
- the one-time payment wallet 160 may launch and may prompt the user to opt-in to provide access to the issuer-specific credential needed for the validated (or trusted) application.
- the embedded Secret Token and/or Application ID are compared to the data in the Card Services Registry on the device. If there is match, the application is trusted and can access the payment subsystem 150 via card service module. In this manner, it can be seen that applications 200 or wallet user interface may also be removed from the Card Services Registry and thus would be disabled from accessing the payment subsystem and possibly the application, altogether.
- Card services module also preferably uses the trusted application verification step to determine the appropriate level of subsystem access allowed for the one-time payment wallet 160.
- the application may be authorized to access and display all of the data contained in the payment subsystem 150, where another application may be only authorized to access and display a subset of the data contained in the payment subsystem 150.
- an application may be permitted only to send a payment or transaction requests to one-time payment wallet 160, but may not itself be permitted to access any of the data contained in the payment subsystem 150.
- assignment of permissions to the application can be thought of as follows: Reserved All Credentials Extended Issuer Own
- the I-BofA-II issuer has permission level 11111, which can be thought to expand to 0001 0001 0001 0001 0001.
- the I-BofA-II application can read, write, delete, activate/deactivate, and download its own credentials but not the extended issuer credentials let alone all credentials. If BofA had another issuer code (e.g. I-BofA-I), then that would be an extended Issuer application.
- the wallet user interface may be given a permission level of 44444 (i.e. 0100 0100 0100 0100 0100). In other words, the wallet user interface can read, write, delete,
- activate/deactivate, and download all credentials As would be understood by those of ordinary skill in the art, these are merely examples of potential permissions that can be granted to applications, other permissions are contemplated. For instance, some applications may have the ability to read extended issuer credentials, but only write, delete, activate and download the application's own credentials (e.g. 21111, which expands to 0010 0001 0001 0001 0001). In yet another example, an application may only be given activate/deactivate and download rights (e.g. 0000 0000 0000 0001 0001 or 00011 in hexadecimal). In yet another example, an application may be disabled— without being deleted from the trusted application database or Card Service Registry— by setting all rights to zero.
- the one-time payment wallet application 160 is configured as one of the trusted third party applications it would have to be registered in order to access Open Wallet 100 (or even card services module).
- the one-time payment wallet application 160 was developed by the issuer associated with issuing engine 2010. Further the one-time payment wallet application 160 may emulate NFC credentials. Accordingly, one-time payment wallet application 160 should be given a permission level 11111, which can be thought to expand to 0001 0001 0001 0001 0001. In other words, the one-time payment wallet application 160 can read, write, delete, activate/deactivate, and download its own credentials but not the extended issuer credentials or any other credentials.
- the foregoing description and drawings refer to a one-time payment wallet 160, and one-time payment credentials or information or temporary payment card data that expires after a short predetermined period of time. It is recognized, however, that the one-time payment wallet 160 may instead be considered a dynamic temporary wallet 160 and that the one-time payment credentials/information and the temporary payment card data may be considered dynamic temporary credentials. As such, credentials may (1) be "recycled” and reused within the system by other users; (2) have a predetermined time to live that is longer than a "short" predetermined period of time and (3) that such credentials can be used for more than simply purchasing merchandise.
- electronic control points may include any access point such as point of sale devices, RFID transceivers, bar code transceivers, NFC transceivers, etc.
- credentials must generally be "paid for" by an issuer 310 or other organization within the overall larger merchant payment system.
- systems may only have a limited number of credentials at its disposal. Using such credentials only one-time for a particular user and transaction can lead to unnecessary high costs compared to a system wherein payment credentials are recycled for use by multiple users at disparate times and, preferably in disparate geo-locations to provide additional security against fraud.
- issuing engine 2010 may track the issuance of and expiration data associated with credentials to a first user operating a first portable communication device 50 located in a first geolocation (e.g., California) and, subsequent to the expiration date and time of the credentials, reassign the very same credentials to a second user operating a second portable communication device 50 located in a second, disparate geolocation (e.g., Florida).
- credentials may have longer time to live periods to permit the use of the credentials at a variety of "points of sale" or other electronic control points.
- FIG. 9A and 9B an exemplary wallet user interface is illustrated on a portable communication device 50.
- Wallet 160 may include and be associated with a variety of payment cards (e.g., MasterCharge, VISA, Charge-It, etc. as illustrated in FIG. 9A) and may further include and be associated with a variety of other non-payment applications (e.g., a room key at a hotel, an office keycard, a rental car FOB, etc. as illustrated in FIG. 9B). While the "time to live" period is preferably short in the context of a sale at a point of sale to provide enhanced security, it is contemplated that the "time to live” may be significantly longer when wallet is associated with non-payment applications such as a room key at a hotel.
- non-payment applications e.g., a room key at a hotel, an office keycard, a rental car FOB, etc.
- the wallet 160 may be used to "open” or “lock” a user's room at a hotel.
- the "time to live” should be set to be at least coextensive with the user's stay at the hotel.
- the time to live can be set to a period of time (infinite if necessary) to permit the user of device 50 to use the device 50 to access an office or a rental car.
- system management back end 300 and issuer 310 may be associated with non- financial services to permit the usage of non-payment wallet applications.
- system management back end 300 may include data relevant to non- financial services (e.g., hotel location, office location, etc.) and that issuer 310 may be affiliated with non-payment entities (e.g., hotel entities, office management entities, etc.).
- An issuer of an electronic payment card may be willing to support extended life dynamic credentials perhaps in certain select circumstances. For instance, a user may wish to make a purchase using a payment credential, but a point of sale terminal may not be connected to a payment network at the time of purchase. Such transactions may be referred to as "offline" transactions. For example, a user may make an in-flight purchase during an airline flight at a point of sale terminal. At some later time, the point of sale terminal may communicate the received payment credential to a payment processing network to request payment from the customer's account. In other instances, the users may desire a temporary payment credential for use from their homes in association with internet-based (or other computer networked commerce) transactions. In still other examples, a user may simply prefer to obtain a temporary payment credential from the comfort of their home, so as to avoid the stress of having to obtain a credential at the right moment in line at the checkout of a retail establishment.
- FIGs 11 A, 1 IB and 12 together illustrate one potential communication flow to obtain a temporary credential and use that credential to make a payment.
- a user may initiate a sign-up process using their wallet application to obtain a temporary payment credential from the cloud.
- the user may have an account (e.g., credit card account debit account, etc.) with a bank (or other financial account provider), and may desire to sign-up for a payment service offered by the bank that permits the user to make payments with temporary payment credentials using their portable communication device 50.
- an account e.g., credit card account debit account, etc.
- a bank or other financial account provider
- the user may obtain a "Temp Pay” card from "Banc Two” by launching the temporary payment wallet application stored on portable communication device 50 that has been previously verified as a trusted application (preferably in the manner illustrated in association with Fig. 10 above).
- the temporary payment wallet application 160 the embedded Secret Token and/or Application ID are compared to the data in the Card Services Registry on the device a local match will enable communication with the mobile banking platform or issuing engine 1102 (see Fig. 11A).
- the temporary dynamic wallet application 160 may generate track data based on the type of temporary payment credential, user data, and contextual data when the user requests the temporary credential.
- This temporary payment card data may preferably be formatted with existing standards and practices of the legacy electronic payment industry, including personal account number, issuer identification number, ISO/IEC 7812 (relating to the identification of issuers using an issuer identification number (UN) to operate in an international, inter-industry, and /or intra-industry interchange), ISO/IEC 7813 (relating to the data structure and content of magnetic tracks used to initial financial transactions), and ISO 8583 formatting (which is a business messaging protocol, based on a proprietary standard).
- ISO/IEC 7812 relating to the identification of issuers using an issuer identification number (UN) to operate in an international, inter-industry, and /or intra-industry interchange
- ISO/IEC 7813 relating to the data structure and content of magnetic tracks used to initial financial transactions
- ISO 8583 formatting which is a business messaging protocol,
- the payment data may be arranged in a format similar to that of track 1 and track 2 data from a conventional credit card, so that the payment data may be processed by a legacy point of sale terminal.
- the payment data may include a data block formed with some or all of the following fields (32 digits): Account # (9 digits); IMEI (device identifier - 11 digits); Expiry date (4 digits); Random number (6); and Sequence counter (2).
- the data block may also include one or more padding characters.
- FIG. 11 A illustrates an example communication flow permitting a user to sign up and obtain a temporary payment credential in one potential embodiment of a process.
- the user may cause their portable communication device 50 to retrieve a wallet application from a mobile banking platform (or issuing engine) 1102 associated with the user's financial account provider, and may create login information that may be subsequently used for authenticating the user.
- a mobile banking platform or issuing engine
- the user may cause portable communication device 50 to open the wallet application and may input the login information.
- the login information may be, for example, a username and password. If the user has multiple accounts, the user may select a particular one to connect to the temporary payment system.
- the issuing engine 1102 may also receive the geo location coordinates received from the portable communication device 50 at the time of this request for later use in association with a payment transaction.
- portable communication device 50 may communicate the login information to mobile banking platform 1102.
- the mobile banking platform 1102 may pass the communication link to the issuer 310 associated with the temporary payment application to ensure that the issuer recognizes the customer.
- issuer 310 may have a Know Your Customer (KYC) Engine capable of communicating with portable communication device 50 without the involvement of the back end system 300. In this way, only the issuer 310 and end user are ever exposed to the end user's personal information.
- the KYC Engine may be capable of generating a user interface on top of the temporary payment application 160 (see Fig. 9C) from which it can directly receive the user input and verify the customer.
- the KYC engine may send an authentication message to the issuing engine 1102.
- mobile banking platform 1102 may return, in block 1112, an acknowledgement message indicating that the user has been authenticated. The user may then, in element 1114, use the wallet application to request to sign up for a temporary payment credential service.
- the mobile banking platform 1102 may generate and communicate a communication security token and a legacy card number to management back end 300.
- the communication security token may be generated and used in accordance with the systems and methods disclosed in Applicant's co-pending patent application serial number 13/916,307 entitled "System and Method for Initially Establishing and Periodically Confirming Trust in a Software Application” filed on June 12, 2013, which is hereby
- mobile banking platform 1102 may communicate the token to portable communication device 50 along with a network identifier.
- the network identifier may identify a network address of management back end 300 for routing messages from the wallet application to management back end 300.
- the network identifier may be a uniform resource identifier (URI).
- portable communication device 50 may communicate the token to management back end 300 using the network identifier.
- management back end 300 may determine whether the user has created a personal identification number (PIN) or other authenticating sequence, and, if not, may communicate, in element 1122, a create PIN message to portable communication device 50.
- PIN personal identification number
- a PIN may be a secret shared by the portable communication device 50 and the system management back end 300 for
- the user may input a desired PIN to the wallet application, and portable communication device 50 may, in element 1124, communicate the created PIN to management back end 300.
- management back end 300 may complete registration of the user and, in element 1128, may generate and communicate a success message to the portable communication device 50.
- the success message may include a temporary payment credential and one or more risk management parameters.
- the temporary payment credential for example, may include randomized card data optionally having a time to live value.
- the temporary payment credential may include routing information, a temporary account identifier, and a checksum.
- the temporary payment credential may include: 6-digit ISO BIN (International Organization for Standardization Bank Identification Number) + 9-digit alternative account identifier + 1 -digit Luhn check.
- the time to live value may be configurable to meet the business rules of the financial account provider.
- the time to live value may have a configurable duration (e.g., seconds, minutes, days, weeks, months, years, etc.) and/or a and may have a configurable usage frequency (e.g., use up to 3 times).
- management back end 300 may request the user's legacy credential data and the Issuer 310 may retrieve and respond with the user's actual credential data.
- Portable communication device 50 may subsequently use the temporary payment credential to make a purchase, including storing the temporary payment credential for offline usage at a later time.
- the user selects the temporary payment credential (e.g. Banc Two Temp Pay) from their wallet application.
- the wallet application may communicate the track data and a legacy bank BIN to a point of sale terminal using, for example, via NFC tap or QR code scan.
- the point of sale terminal may route the track data to its payment processing network, which may process the bank BIN to forward the track data to a third-party Internet-hosted service.
- the third-party Internet-hosted service may assess risk, provide a score, and generate request payment authorization from a bank
- the cloud service may communicate an approval message to the point of sale terminal, thus completing the sale.
- FIG. 12 illustrates a payment communication flow using a temporary payment credential in one potential embodiment of a process.
- a user may launch the trusted wallet application and select which credential to use to make payment.
- wallet application may provide access to multiple payment credentials, some of which may be temporary payment credentials and others may store payment credentials storing legacy card data (e.g., actual payment account information).
- the user may select a temporary payment credential, and enter its corresponding PIN.
- wallet application may generate payment data for the selected temporary payment credential, which is then provided to the Merchant POS Terminal 75 in the same manner described above in association with Figures 7 A and 7B.
- the POS terminal 75 may verify whether the generated data corresponds to an expected format.
- POS terminal 75 may decline the transaction locally. If the format matches expected parameters but the POS terminal is not connected to the merchant payment network, the POS terminal may still approve the transaction offline and complete the sale via the merchant payment network at a later time, in accordance with the following flow.
- the POS terminal 75 communicates parameters of the transaction via an authorization message to the merchant payment network.
- the authorization message may include the Trackl/Track2 data, the merchant ID (and preferably the merchant's geo location), and the amount of the transaction.
- payment network system 1204 may process the authorization message, determine that it contains data for routing to management back end 300, and reroute the authorization message to validation mapping gateway 2020.
- validation mapping gateway 2020 creates a risk score for the transaction based on information that is preferably encoded in the temporary payment card data and using information stored in the mapping gateway database. This risk score may take into account, for example, one or more of the following factors (alone or in combination with one another):
- the age of the credential may be compared with the difference in geo location to provide a significant risk assessment.
- the credential was issued less than an hour earlier but at a geo location hundreds of miles from the current merchant to which it is being presented for redemption, the transaction would be suspect.
- the various parameters may be considered by the risk scoring engine to create a risk score.
- This risk score along with the legacy payment data may be passed to the issuer for an authorization decision as a second authorization message, step 1222.
- Issuer 310 may process the second Track 1/Track 2 data to determine whether to authorize the transaction. If authorized, Issuer 310 may respond to management back end 300 in element 1224 with an authorized message.
- Management back end 300 may map the second Track 1/Track 2 data back to the first Track 1/Track 2 data, and forward to the payment network system 1204 a second authorized message.
- the Issuer may also receive information about the user's digital device signature, such that the Issuer may communicate directly with the end user via device 50 to request input of the CVV (see Figure 9D). The issuer may use that information to further validate the transaction.
- payment network system 1204 optionally may forward the second authorized message to the POS terminal 1202.
- the POS terminal will batch reconcile at end of day with the payment network system 1204.
- the POS terminal will collect all the authorization messages as proof of liability transfer to the issuing bank.
- POS terminal 1202 optionally may wait to approve a transaction until the receipt of the second authorized message.
- the geo-location data would be captured at the time of authorization rather than (or in addition to) the time of issuance, by the portable device payment wallet.
- the geo location data may also be encoded by the payment wallet into the data format (e.g. discretionary data fields of Track 1/Track 2 data format) that will be redeemed at the POS or access point.
- the back-end risk engines can then score the risk associated with redemption of a previously issued one-time token at the specific merchant or facility identified by the geolocation data. But in this new method, the token can be issued well in advance of use and it can be refreshed as policy requires, to minimize the threat of theft or misuse.
- the dynamic credentials/payment tokens may also be limited in some aspects
- embodiments to a "one time” use They might be used repeatedly within a specified date or time range (e.g.) subject to velocity limits and other redemption policies. It is also contemplated that the dynamic credentials may be redeemable only at specific merchants or only within specific redemption limits (amount, date, time of day). We should be specific that this supports physical access applications (e.g. hotel door, campus building), not just payment. These tokens might also be issued well in advance of use.
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- General Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- Strategic Management (AREA)
- Finance (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer Security & Cryptography (AREA)
- Signal Processing (AREA)
- Economics (AREA)
- Development Economics (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/052,640 US20140040139A1 (en) | 2011-12-19 | 2013-10-11 | System and method for dynamic temporary payment authorization in a portable communication device |
PCT/US2014/060145 WO2015088638A1 (en) | 2013-10-11 | 2014-10-10 | System and method for dynamic temporary payment authorization in a portable communication device |
Publications (2)
Publication Number | Publication Date |
---|---|
EP3055818A1 true EP3055818A1 (en) | 2016-08-17 |
EP3055818A4 EP3055818A4 (en) | 2017-06-07 |
Family
ID=53371668
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP14869040.7A Ceased EP3055818A4 (en) | 2013-10-11 | 2014-10-10 | System and method for dynamic temporary payment authorization in a portable communication device |
Country Status (5)
Country | Link |
---|---|
EP (1) | EP3055818A4 (en) |
KR (1) | KR102495688B1 (en) |
AU (1) | AU2014360806A1 (en) |
CA (1) | CA2927318A1 (en) |
WO (1) | WO2015088638A1 (en) |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10505940B2 (en) | 2015-06-19 | 2019-12-10 | Capital One Services, Llc | Systems and methods for managing electronic tokens for device interactions |
WO2017074281A1 (en) * | 2015-10-27 | 2017-05-04 | DOGAN, Mustafa Cemal | Multi-dimensional authentication system and method for cardless banking transactions and other transactions involving high-level security |
WO2019045672A1 (en) * | 2017-08-28 | 2019-03-07 | Visa International Service Association | System, method, and computer program product for dynamic application selection |
CN111489148B (en) * | 2019-01-28 | 2023-11-21 | ***通信有限公司研究院 | Risk control method and device, electronic equipment and storage medium |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8572391B2 (en) * | 2003-09-12 | 2013-10-29 | Emc Corporation | System and method for risk based authentication |
US8424061B2 (en) * | 2006-09-12 | 2013-04-16 | International Business Machines Corporation | Method, system and program product for authenticating a user seeking to perform an electronic service request |
KR100996910B1 (en) * | 2008-07-09 | 2010-11-29 | 고려대학교 산학협력단 | System and Method of Location-based information security |
US20100024017A1 (en) * | 2008-07-22 | 2010-01-28 | Bank Of America Corporation | Location-Based Authentication of Online Transactions Using Mobile Device |
US20120123868A1 (en) * | 2010-11-17 | 2012-05-17 | David Brudnicki | System and Method for Physical-World Based Dynamic Contactless Data Emulation in a Portable Communication Device |
US20120265685A1 (en) * | 2010-11-17 | 2012-10-18 | Sequent Software Inc. | System and Method for Physical-World Based Dynamic Contactless Data Emulation in a Portable Communication Device |
US9898728B2 (en) * | 2011-12-19 | 2018-02-20 | Gfa Worldwide, Inc. | System and method for one-time payment authorization in a portable communication device |
-
2014
- 2014-10-10 KR KR1020167012355A patent/KR102495688B1/en active IP Right Grant
- 2014-10-10 EP EP14869040.7A patent/EP3055818A4/en not_active Ceased
- 2014-10-10 AU AU2014360806A patent/AU2014360806A1/en not_active Abandoned
- 2014-10-10 WO PCT/US2014/060145 patent/WO2015088638A1/en active Application Filing
- 2014-10-10 CA CA2927318A patent/CA2927318A1/en not_active Abandoned
Also Published As
Publication number | Publication date |
---|---|
KR20160071421A (en) | 2016-06-21 |
WO2015088638A1 (en) | 2015-06-18 |
EP3055818A4 (en) | 2017-06-07 |
KR102495688B1 (en) | 2023-02-06 |
CA2927318A1 (en) | 2015-06-18 |
AU2014360806A1 (en) | 2016-05-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20220358484A1 (en) | System and Method for Dynamic Temporary Payment Authorization in a Portable Communication Device | |
JP6818727B2 (en) | Systems and methods for dynamic temporary payment authentication in mobile communication devices | |
US10515352B2 (en) | System and method for providing diverse secure data communication permissions to trusted applications on a portable communication device | |
US20120123935A1 (en) | System and Method for Physical-World Based Dynamic Contactless Data Emulation in a Portable Communication Device | |
US20120159612A1 (en) | System for Storing One or More Passwords in a Secure Element | |
US20170178116A1 (en) | Remote transaction system, method and point of sale terminal | |
KR20140058442A (en) | System and method for performing a secure transaction | |
AU2023200221A1 (en) | Remote transaction system, method and point of sale terminal | |
KR102495688B1 (en) | System and method for dynamic temporary payment authorization in a portable communication device | |
WO2013130651A2 (en) | System for storing one or more passwords in a secure element |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20160510 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
DAX | Request for extension of the european patent (deleted) | ||
A4 | Supplementary search report drawn up and despatched |
Effective date: 20170509 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: G06Q 20/40 20120101ALI20170502BHEP Ipc: G06Q 20/38 20120101ALI20170502BHEP Ipc: G06Q 20/36 20120101ALI20170502BHEP Ipc: G06Q 20/22 20120101ALI20170502BHEP Ipc: G06Q 20/32 20120101ALI20170502BHEP Ipc: G06Q 20/20 20120101AFI20170502BHEP |
|
17Q | First examination report despatched |
Effective date: 20180328 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: SEQUENT SOFTWARE INC. |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R003 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED |
|
18R | Application refused |
Effective date: 20201126 |