TOKENIZATION IN PAYMENT ENVIRONMENTS

• US 20130212007A1
• Filed: 02/06/2013
• Published: 08/15/2013
• Est. Priority Date: 02/10/2012
• Status: Abandoned Application

• Current Assignee: Protegrity USA, Inc. (Xcelera Inc.)
• Original Assignee: Protegrity USA, Inc. (Xcelera Inc.)
• Inventors: Mattsson, Ulf, Rozenberg, Yigal
• Application Number:
  US13/761,009
• Publication Number:
  US 20130212007A1
• Time in Patent Office: Days
• US Class Current: 705/39
• CPC Class Codes: G06F 21/606 by securing the transmission between two devices or processes
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 20/326 Payment applications installed on the mobile devices
• CPC Class Codes: G06Q 20/34 using cards, e.g. integrated circuit [IC] cards or magnetic cards
• CPC Class Codes: G06Q 20/367 involving electronic purses or money safes
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/3821 Electronic credentials
• CPC Class Codes: G06Q 20/3823 combining multiple encryption tools for a transaction
• CPC Class Codes: G06Q 20/3829 involving key management
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules
• CPC Class Codes: G06Q 2220/00 Business processing using cryptography postage metering system using cryptography G06Q2250/05
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04W 12/02 Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
• CPC Class Codes: H04W 12/03 Protecting confidentiality, e.g. by encryption

Abstract

Data can be protected in mobile and payment environments through various tokenization operations. A mobile device can tokenize communication data based on device information and session information associated with the mobile device. A payment terminal can tokenize payment information received at the payment terminal during a transaction based on transaction information associated with the transaction. Payment data tokenized first a first set of token tables and according to a first set of tokenization parameters by a first payment entity can be detokenized or re-tokenized with a second set of token tables and according to a second set of tokenization parameters. Payment information can be tokenized and sent to a mobile device as a token card based on one or more selected use rules, and a user can request a transaction based on the token card. The transaction can be authorized if the transaction satisfies the selected use rules.

Claims

1. A method for processing payment information, comprising:

receiving, at a payment terminal, payment information associated with a transaction;

identifying transaction information associated with the transaction;

identifying a set of tokenization parameters based on the transaction information;

tokenizing the payment information based on the set of tokenization parameters; and

responsive to the payment terminal being communicatively coupled to a central payment system, transmitting the tokenized payment information to the central payment system.

2. The method of claim 1, wherein the received payment information comprises a credit card number.

3. The method of claim 1, wherein the received payment information comprises a bank account number.

4. The method of claim 1, wherein the identified transaction information comprises a transaction cost.

5. The method of claim 1, wherein the identified transaction information comprises the identity of a merchant associated with the transaction.

6. The method of claim 1, wherein the identified transaction information comprises the identity of a user associated with the transaction.

7. The method of claim 1, wherein the identified transaction information comprises a payment method associated with the received payment information.

8. The method of claim 1, wherein the identified transaction information comprises a time and date associated with the transaction.

9. The method of claim 1, wherein the set of tokenization parameters comprises an identity of one or more token tables stored at the payment terminal.

10. The method of claim 9, wherein tokenizing the payment information comprises:

querying an identified token table with a portion of the payment information to obtain a token; and

replacing the portion of the payment information with the token.

11. The method of claim 1, wherein the set of tokenization parameters comprises a number of tokenization iterations.

12. The method of claim 1, wherein the set of tokenization parameters comprises a token table seed value, and wherein tokenizing the payment information comprises:

generating one or more token tables based on the token table seed value; and

tokenizing the payment information using the one or more generated token tables.

13. The method of claim 1, wherein the central payment system is configured to store tokenized payment information associated with a plurality of transactions.

14. The method of claim 13, wherein, in response to the central payment system storing tokenized payment information associated with a threshold number of transactions, the central payment system is configured to transmit the stored tokenized payment information to a payment entity associated with the transactions.

15. The method of claim 1, further comprising:

responsive to the payment terminal being communicatively uncoupled from the central payment system, storing the tokenized payment information at the payment terminal; and

in response to the payment terminal being subsequently communicatively coupled to the central payment system, transmitting the stored tokenized payment information to the central payment system.

16. The method of claim 1, wherein transmitting the tokenized payment information to the central payment system comprises:

receiving a request for tokenized payment information from the central payment system; and

transmitting the tokenized payment information in response to the received request.

17. The method of claim 1, further comprising:

receiving, from the central payment system, a set of token tables for use in tokenizing the payment information.

18. A payment terminal for processing payment information, configured to:

receive payment information associated with a transaction;

identify transaction information associated with the transaction;

identify a set of tokenization parameters based on the transaction information;

tokenize the payment information based on the set of tokenization parameters; and

responsive to the being communicatively coupled to a central payment system, transmit the tokenized payment information to the central payment system.

19. A method for processing payment information, comprising:

receiving, at a payment terminal, payment information associated with a transaction;

accessing a set of token tables based on the transaction;

tokenize the payment information using the set of token tables; and

responsive to the payment terminal being communicatively coupled to a central payment system, transmitting the tokenized payment information to the central payment system.

20. A payment terminal for processing payment information, configured to:

receive payment information associated with a transaction;

access a set of token tables based on the transaction;

tokenize the payment information using the set of token tables; and

responsive to being communicatively coupled to a central payment system, transmit the tokenized payment information to the central payment system.