Patent Application
20160358163
The present disclosure relates to computing systems, and, in particular, to computing system supporting secure payment through tokenization.
As payments technology evolves, new types of payment systems and techniques are being used to provide increased protection against counterfeit, account misuse, and other types of fraud. One technique that has been used is known as payment tokenization, which involves substituting a payment Primary Account Number (PAN) with a payment token in the payments ecosystem. Payment tokens may be used to originate payment transactions, while non-payment tokens may be used for other purposes, such as loyalty program tracking. A payment token service provider may be authorized to provide payment tokens to token requestors, such as card on file merchants, acquirer processors, payment gateways, digital wallet providers, card issuers, and the like. The token service provider may be implemented to run on a server and to receive requests for payment tokens from one or more token requestors. For each payment token request, the token service provider generates a random payment token, which is in some cases a Bank Identification Number (BIN)/Issuer Identification Number (IIN) range that is not currently being used by any active payment card. The token may be given some expiration period and can be used in place of the PAN for a payment card until it expires. Before the token expires, however, a hostile actor may eavesdrop on financial transaction communications in an attempt to determine what payment card number maps to a particular token.
Another potential security threat may stem from the use of mobile devices, which need to be online to request token(s) from the payment token service provider. An alternative is to pre-populate a mobile device with some number of payment tokens. Such an approach, however, may involve extra administration overhead at the payment token service provider, and the tokens may risk a greater likelihood of being compromised due to mobile devices being more susceptible to being stolen, misplaced, or compromised in some way.
In some embodiments of the inventive subject matter, a method comprises communicating with a token server to identify a key, generating an initialization vector, performing a logical operation on the key using the initialization vector to generate a modified key, encrypting a financial account number using a format preserving encryption technique to generate a payment token where the format preserving encryption technique uses the modified key, establishing a communication connection with a point-of-sale terminal, and transmitting the payment token to the point-of-sale terminal.
In other embodiments of the inventive subject matter, a method comprises communicating with a user device to identify a key, receiving a payment token from an issuer data processing system associated with a financial account number, determining an initialization vector used to generate the payment token, performing a logical operation on the key using the initialization vector to generate a modified key, decrypting the payment token using a format preserving encryption technique to obtain the financial account number where the format preserving encryption technique uses the modified key, and communicating the financial account number to the issuer data processing system.
In further embodiments of the inventive subject matter, a computer program product comprises a tangible computer readable storage medium. The tangible computer readable storage medium comprises computer readable program code embodied in the medium that when executed by a processor causes the processor to perform operations comprising: communicating with a token server to identify a key, generating an initialization vector, performing a logical operation on the key using the initialization vector to generate a modified key, encrypting a financial account number using a format preserving encryption technique to generate a payment token where the format preserving encryption technique uses the modified key, establishing a communication connection with a point-of-sale terminal, and transmitting the payment token to the point-of-sale terminal.
Other methods, systems, articles of manufacture, and/or computer program products according to embodiments of the inventive subject matter will be or become apparent to one with skill in the art upon review of the following drawings and detailed description. It is intended that all such additional systems, methods, articles of manufacture, and/or computer program products be included within this description, be within the scope of the present inventive subject matter, and be protected by the accompanying claims. Moreover, it is intended that all embodiments disclosed herein can be implemented separately or combined in any way and/or combination.
Other features of embodiments will be more readily understood from the following detailed description of specific embodiments thereof when read in conjunction with the accompanying drawings, in which:
In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. However, it will be understood by those skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components and circuits have not been described in detail so as not to obscure the present invention. It is intended that all embodiments disclosed herein can be implemented separately or combined in any way and/or combination.
As used herein, a “service” includes, but is not limited to, a software and/or hardware service, such as cloud services in which software, platforms, and infrastructure are provided remotely through, for example, the Internet. A service may be provided using Software as a Service (SaaS), Platform as a Service (PaaS), and/or Infrastructure as a Service (IaaS) delivery models. In the SaaS model, customers generally access software residing in the cloud using a thin client, such as a browser, for example. In the PaaS model, the customer typically creates and deploys the software in the cloud sometimes using tools, libraries, and routines provided through the cloud service provider. The cloud service provider may provide the network, servers, storage, and other tools used to host the customer's application(s). In the IaaS model, the cloud service provider provides physical and/or virtual machines along with hypervisor(s). The customer installs operating system images along with application software on the physical and/or virtual infrastructure provided by the cloud service provider.
As used herein, the term “data processing facility” includes, but it not limited to, a hardware element, firmware component, and/or software component. A data processing system may be configured with one or more data processing facilities.
As used herein, the term “mobile terminal” or “mobile device” may include a satellite or cellular radiotelephone with or without a multi-line display; a Personal Communications System (PCS) terminal that may combine a cellular radiotelephone with data processing, facsimile and data communications capabilities; a PDA or smart phone that can include a radiotelephone, pager, Internet/intranet access, Web browser, organizer, calendar and/or a global positioning system (GPS) receiver; and a conventional laptop and/or palmtop receiver or other appliance that includes a radiotelephone transceiver. Mobile terminals or mobile devices may also be referred to as “pervasive computing” devices.
Some embodiments of the inventive subject matter stem from a realization that a purchaser can use a mobile device to make a payment in which the mobile device generates a secure payment token using Format Preserving Encryption (FPE) to take the place of the Primary Account Number (PAN) in the payment ecosystem. In particular, the secure token is generated using FPE along with a dynamic initialization vector so that even if a hostile entity were to discover the keys used in the FPE operation, a PAN will not map to the same secure payment token number every time. The dynamic initialization vector may be based on such parameters as an expiration date for the payment token, a timestamp comprising both a current date and a current time that the payment token is transmitted to a point-of-sale (POS) terminal, an issuer identification number portion of the PAN, and/or a prime number.
A shopper may provide payment information to the POS terminal 110 using a mobile device 105 that may include links to financial accounts thereon and/or data identifying various financial accounts, such as credit card accounts, store credit accounts, debit card accounts, checking accounts, loyalty program accounts, rewards accounts, and the like. The mobile device 105 may also include identification credentials, such as a photo identification, driver's license, passport, insurance card, home and/or work address information, home and/or work telephone numbers, and the like. In some embodiments, the financial information and/or personal identification information may be managed using a digital wallet application residing on the phone or in a cloud server on the Internet or other network.
The mobile device 105 may be configured to make a payment by generating a secure payment token locally using FPE to take the place of the PAN in the financial transaction. The secure payment token may be generated using FPE along with a dynamic initialization vector to ensure that the PAN will not map to the same secure payment token number every time a payment is made. The dynamic initialization vector may be based on such parameters as an expiration date for the payment token, a timestamp comprising both a current date and a current time that the payment token is transmitted to the POS terminal 110, an issuer identification number portion of the PAN, and/or a prime number. Unlike some conventional payment systems in which payment tokens are used, the mobile device 105 need not be online to request a token from a payment server.
As shown in
The issuer server 125 is coupled to a token server 130 via a secure connection. The secure payment token generated by the mobile device 105 is communicated to the issuer server 125 through the payment network 120. The issuer server 125, however, cannot determine the actual PAN used in the financial transaction from the secure payment token. Thus, the issuer server 125 communicates the secure payment token along with initialization vector information, such as expiration date for the secure payment token and/or the date that the secure payment token was transmitted to the merchant POS terminal 110 to initiate the transaction, to the token server 130 over a secure communication connection using, for example, Transport Layer Security (TLS) or Secure Socket Layer (SSL) protocols. As described above, the initialization vector may be based on such parameters as an expiration date for the payment token, a timestamp comprising both a current date and a current time that the payment token is transmitted to the POS terminal 110, an Issuer Identification Number (IIN) portion of the PAN, and/or a prime number. The prime number along with key(s) used in encrypting the PAN to generate the secure payment token may be agreed upon through one or more communication sessions between the token server 130 and the mobile device 105 over the Internet 135. These communication sessions may also be used to provide the token server 130 with information on what information the mobile device 105 uses to generate the initialization vector, i.e., expiration date for the payment token and/or a timestamp comprising both a current date and a current time that the payment token is transmitted to the POS terminal 110. The token server 130 may determine the initialization vector used in generating the secure payment token and, with knowledge of the key(s) used in the FPE operations by the mobile device 105, the token server 130 may decrypt the secure payment token to obtain the PAN. The token server 130 may communicate the PAN to the issuer server 125 over the secure connection with the issuer server 125 to allow the issuer server 125 to continue with settlement of the transaction by sending funds for the transaction to the merchant's account at the acquirer server 115.
The connections between the mobile device 105, POS terminal 110, acquirer server 115, issuer server 125, and token server 130 may include wireless and/or wireline connections and may be direct or include one or more intervening local area networks, wide area networks, and/or the Internet. The payment network 120 may be a global network, such as the Internet or other publicly accessible network. Various elements of the payment network 120 may be interconnected by a wide area network, a local area network, an Intranet, and/or other private network, which may not be accessible by the general public. Thus, the payment network 120 may represent a combination of public and private networks or a virtual private network (VPN). The payment network 120 may be a wireless network, a wireline network, or may be a combination of both wireless and wireline networks.
Although
Referring now to
As shown in
The data exchange module 325 may be configured to communicate with the mobile device 105 to agree upon the prime number along with key(s) used in encrypting the PAN to generate the secure payment token. The data exchange module 325 may be further used to obtain information on what information the mobile device 105 uses to generate the initialization vector, i.e., expiration date for the payment token and/or a timestamp comprising both a current date and a current time that the payment token is transmitted to the POS terminal 110.
The initialization vector determination module 330 may be configured to receive the secure payment token from the issuer server 125 and, based on the IIN, the expiration date for the payment token and/or the timestamp comprising both the current date and the current time that the payment token is transmitted to the POS terminal 110, and the prime number, determine the initialization vector.
The token decryption module 335 may be configured to decrypt the secure payment token received from the issuer server 125 based on the initialization vector determined by the initialization vector determination module 330 and knowledge of the key(s) used in the FPE operations by the mobile device 105 to obtain the PAN.
The communication module 340 may be configured to facilitate communication between the token server 130 and the mobile device 105 to support, for example, the data exchange module 325 as well as communication with the issuer server 125 to receive the secure payment token and to send the PAN back to the issuer server 125 after the secure payment token is decrypted.
Although
Referring now to
The processor 440 communicates with the memory 435 via an address/data bus. The processor 440 may be, for example, a commercially available or custom microprocessor. The memory 435 is representative of the one or more memory devices containing the software and data used to facilitate secure payment transactions via tokenization using FPE, in accordance with some embodiments of the present invention. The memory 435 may include, but is not limited to, the following types of devices: cache, ROM, PROM, EPROM, EEPROM, flash, SRAM, and DRAM.
As shown in
The data exchange module 470 may be configured to communicate with the token server 130 to agree upon the prime number along with key(s) used in encrypting the PAN to generate the secure payment token. The data exchange module 470 may be further used to share information with the token server 130 on what the mobile device 105 uses to generate the initialization vector, i.e., expiration date for the payment token and/or a timestamp comprising both a current date and a current time that the payment token is transmitted to the POS terminal 110.
The initialization vector generation module 475 may be configured to generate the initialization vector based on the IIN, the expiration date for the payment token and/or the timestamp comprising both the current date and the current time that the payment token is transmitted to the POS terminal 110, and the prime number.
The token generation module 480 may be configured to generate a secure payment token locally using FPE to take the place of the PAN in a financial transaction. The secure payment token may be generated using FPE along with the dynamic initialization vector provided by the initialization vector generation module 475. In some embodiments, the FPE operation may comprise a multiple round Feistel Network cipher using a different key in each of the rounds. The round function used in the Feistel Network cipher may be an Advanced Encryption Standard (AES) cipher.
The Feistel Network cipher operates as follows: The input, which may be the PAN in accordance with embodiments of the present inventive subject matter, may be broken into two parts: a left part L and a right part R. The part is logically combined through an exclusive OR operation with the encrypted value obtained using the plain text of the right part as input. The AES cipher is used in the encryption operation F( ) performed on the right part and the key. A different key may be used for each round. Moreover, the key may be modified with the initialization vector provided by the initialization vector generation module 475. In some embodiments, the modified key is obtained by performing a logical OR operation on the key and the initialization vector. Just as a different key value may be used in each round of the encryption operations, a different initialization vector may be used in each round of the encryption operation according to some embodiments of the inventive subject matter. The input text is padded and the padded value is truncated post encryption. This makes the process reversible and may help in the decryption operations. Formulas used for the encryption and decryption operations are set forth below. K represents the key modified with the initialization vector:
Encryption:
For each round i=0, 1, . . . , n, compute
L
i+1
=R
i
R
i+1
=L
i
⊕F(Ri, Ki).
Then the cipher text is (Rn+1, Ln+1).
Decryption:
Decryption of a cipher text (Rn+1, Ln+1) is accomplished by computing for i=n, n−1, . . . , 0
R
i
=L
i+1
L
i
=R
i+1
⊕F(Li+1, Ki).
Then (L0, R0) is the plaintext again.
The communication module 485 may be configured to facilitate communication between the mobile device 105 and the token server 130 to support, for example, the data exchange module 470 as well as communication with the merchant POS terminal 110 to transmit the secure payment token in place of a PAN during a financial transaction.
Although
Computer program code for carrying out operations of data processing systems discussed above with respect to
Moreover, the functionality of the mobile device 105 of
The mobile device 105 at block 505 may generate the initialization vector using the initialization vector generation module 475. In some embodiments, the initialization vector may be generated by multiplying an expiration date for the payment token, the IIN portion of the PAN, and the prime number together. In other embodiments, the initialization vector may be generated by multiplying a timestamp comprising both a current date and a current time that the payment token is transmitted to the merchant POS terminal 110, the IIN portion of the PAN, and the prime number together. The data exchange module 470 may be used to share information with the token server 130 on what the mobile device 105 uses to generate the initialization vector, i.e., expiration date for the payment token and/or a timestamp comprising a current date and a current time that the payment token is transmitted to the POS terminal 110.
At block 510, the token generation module 480 uses the initialization vector to generate the modified key and, at block 515, encrypt the PAN using the modified key to generate the payment token. As described above, a multiple round Feistel Network cipher may be used as the FPE technique to generate the secure payment token. A different initialization vector may be generated and a different key may be used for each round.
At block 520, a communication connection may be established with the merchant POS terminal using, for example, but not limited to, NFC functionality, scanning a bar code, scanning a QR code, scanning text information, and the like. The secure payment token can then be used in the payment ecosystem of
Referring now to
The systems, methods, and computer program products described herein regarding facilitating secure payment transactions via tokenization using FPE may be applied in a variety of different ways to enhance the operation of mobile devices, merchant servers, and bank/financial entity servers through improved security. Embodiments of the present inventive concept may be used in the authorization process, the settlement process, the merchant initiated reversal process, and/or the issuer initiated reversal (chargeback) process associated with financial transactions.
The authorization process, according to some embodiments, involves the mobile device generating a secure payment token using one or more keys and one or more initialization vectors. The secure payment token is used in place of a PAN for conducting a financial transaction and is provided to the merchant POS terminal. The merchant transmits the secure payment token along with other transaction details to the acquirer (e.g., merchant bank). The acquirer forwards the token along with the other transaction details through the payment network to the issuer. The issuer communicates with the token server to send the secure payment token along with the token expiration date, for example, which the token server uses to decrypt secure payment token to obtain the original PAN. The PAN is then forwarded back to the issuer through a secure communication channel.
The settlement process, according to some embodiments, is similar to the authorization process and involves a merchant submitting the transaction details (including the secure payment token) via the acquirer through the payment network to the issuer. The issuer communicates with the token server to send the secure payment token along with the token expiration date, for example, to get the token server to decrypt the secure payment token and obtain the original PAN. The token server sends the PAN back to the issuer who then proceeds with transferring funds in the amount of the transaction to the acquirer (e.g., merchant's bank).
The merchant initiated reversal process, according to some embodiments, involves the merchant sending the actual PAN details for a transaction through the acquirer to the issuer via the payment network. The issuer may then communicate with the token server to obtain audit and/or log information from the token server regarding the transaction to assist the issuer in communicating with the acquirer to refund the cost of the transaction to the customer's account. Sending the actual PAN details, however, may be less secure so the merchant may instead send a secure payment token instead by having, for example, the customer swipe/tap a smart phone or credit card instead. The process is similar, but the token server will now decrypt the secure payment token to obtain the PAN for the issuer.
The issuer initiated reversal, according to some embodiments, involves the issuer sending the actual card details, e.g., PAN, to the token server to obtain audit and/or log information associated with a particular transaction to assist the issuer in refunding the transaction cost to the customer's account.
The systems, methods, and computer program products described herein regarding facilitating secure payment transactions via tokenization using FPE may improve the operation of mobile devices, merchant servers, and/or bank/financial entity servers through improved security. An initialization vector generated for each round of a Feistel Network encryption process, for example, can ensure that a different payment token is obtained every time a PAN is encrypted. This makes secure payment token dynamic and increases the level of security. Moreover, the embodiments described herein provide an additional advantage in that the customer's mobile device may generate the secure payment token and a token server may decrypt the payment token as both entities are informed about what key(s) are used and what initialization vector is used as part of the encryption process.
Although the embodiments described herein have been directed to generating a secure payment token locally at a mobile device, such as mobile device 105, using FPE to take the place of a PAN in a financial transaction, in other embodiments, secure payment tokens may be generated in bulk on a token server, such as token server 130. The token server may then pre-populate the mobile device with tokens over the Internet 135, for example, at various times, upon request, and/or periodically. Such operations may be termed replenishment of the tokens on the mobile device. In some embodiments, when the mobile device is replenished with tokens from the token server, basing the dynamic initialization vector on the expiration date for the payment token along with an issuer identification number portion of the PAN and/or a prime number may be desirable.
In the above-description of various embodiments of the present disclosure, aspects of the present disclosure may be illustrated and described herein in any of a number of patentable classes or contexts including any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof. Accordingly, aspects of the present disclosure may be implemented entirely hardware, entirely software (including firmware, resident software, micro-code, etc.) or combining software and hardware implementation that may all generally be referred to herein as a “circuit,” “module,” “component,” or “system.” Furthermore, aspects of the present disclosure may take the form of a computer program product comprising one or more computer readable media having computer readable program code embodied thereon.
Any combination of one or more computer readable media may be used. The computer readable media may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an appropriate optical fiber with a repeater, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable signal medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C++, C#, VB.NET, Python or the like, conventional procedural programming languages, such as the “C” programming language, Visual Basic, Fortran 2003, Perl, COBOL 2002, PHP, ABAP, dynamic programming languages such as Python, Ruby and Groovy, or other programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider) or in a cloud computing environment or offered as a service such as a Software as a Service (SaaS).
Aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable instruction execution apparatus, create a mechanism for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that when executed can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions when stored in the computer readable medium produce an article of manufacture including instructions which when executed, cause a computer to implement the function/act specified in the flowchart and/or block diagram block or blocks. The computer program instructions may also be loaded onto a computer, other programmable instruction execution apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatuses or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various aspects of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The terminology used herein is for the purpose of describing particular aspects only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items. Like reference numbers signify like elements throughout the description of the figures.
The corresponding structures, materials, acts, and equivalents of any means or step plus function elements in the claims below are intended to include any disclosed structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present disclosure has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the disclosure in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the disclosure. The aspects of the disclosure herein were chosen and described in order to best explain the principles of the disclosure and the practical application, and to enable others of ordinary skill in the art to understand the disclosure with various modifications as are suited to the particular use contemplated.
