Configurable payment tokens

• US 9,256,871 B2
• Filed: 07/26/2012
• Issued: 02/09/2016
• Est. Priority Date: 07/26/2012
• Status: Active Grant

• Current Assignee: Visa USA, Inc. (Visa, Inc.)
• Original Assignee: Visa USA, Inc. (Visa, Inc.)
• Inventors: Anderson, Lisa, Cushley, Seamus, Downey, Fergal
• Primary Examiner(s): AGWUMEZIE, CHINEDU CHARLES
• Application Number:
  US13/558,979
• Publication Number:
  US 20140032419A1
• Time in Patent Office: 1,293 Days
• Field of Search: 705/78
• US Class Current: 1/1
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/227 characterised in that multiple accounts are available, e.g. to the payer
• CPC Class Codes: G06Q 20/3672 initialising or reloading thereof
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 20/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

Abstract

Methods and systems are disclosed for the generation and use of merchant-customizable token formats that define tokens that represent credit card and other payment numbers in online transactions. The tokens, which are used instead of the card numbers themselves for security, can be specified by the token format to have a certain number of characters, have certain fields reserved for major card identifiers, use encryption and/or randomization, be alphanumeric, and have other formatting. The customized tokens can be used with legacy equipment that uses longer or shorter card numbers than the standard sixteen-digit payment card number format and can be less likely to be recognized as related to card numbers by identify thieves.

Claims

1. A method comprising:

receiving, by a payment processor computer, via a graphical user interface on a merchant computer operated by a merchant, a merchant-configured token format from the merchant, wherein the graphical user interface is configured to allow the merchant to specify a length of characters or character set in the merchant-configured token format, wherein the merchant-configured token format specifies at least one of the length and characters of tokens to be generated;

after receiving the merchant-configured token format, storing, by the payment processor computer, the merchant-configured token format received from the merchant computer in a database;

after the merchant-configured token format is stored, receiving, by the payment processor computer, from the merchant, a payment account number from a customer during a first transaction with the merchant;

generating or receiving, by the payment processor computer, an authorization request message comprising the payment account number;

sending, by the payment processor computer, the authorization request message comprising the payment account number to an issuer computer associated with the payment account number;

receiving, by the payment processor computer, an authorization response message comprising the payment account number from the issuer computer;

after receiving the authorization response message from the issuer computer, retrieving, by the payment processor computer, the merchant-configured token format from the database;

generating, by the payment processor computer, a token associated with the payment account number using the retrieved merchant-configured token format, the token including a set of characters, wherein the token conforms to the merchant-configured token format; and

sending, by the payment processor computer, to the merchant the token associated with the payment account number, wherein the token is stored at the merchant.

2. The method of claim 1 wherein the merchant-configured token format specifies a total number of characters for the tokens to be generated.

3. The method of claim 2 wherein the specified total number of characters for the token is different than a number of total characters of the payment account number.

4. The method of claim 1 wherein the generating the token includes:

encrypting a portion of the payment account number; and

building the token using the encrypted portion of the payment account number.

5. The method of claim 1 wherein the merchant-configured token format specifies one or more characters indicating a particular payment network.

6. The method of claim 1 wherein the merchant-configured token format specifies that only letters are in the tokens to be generated.

7. The method of claim 1 wherein the merchant-configured token format specifies that only numbers are in the tokens to be generated.

8. The method of claim 1 wherein the payment account number identifies an account associated with a card selected from the group consisting of a credit card, debit card, and prepaid card.

9. The method of claim 1 wherein the characters include only those specified by the American Standard Code for Information Exchange (ASCII).

10. The method of claim 1 wherein the generated token is not mod 10 compliant.

11. The method of claim 1 wherein the merchant-configured token format further specifies a position where a portion of the token is generated using a random number generator.

12. The method of claim 1 further comprising:

receiving a selection of the token at the merchant;

receiving the token at the payment processor computer;

determining, by the payment processor computer, the payment account number associated with the token;

generating or receiving, by the payment processor computer, a second authorization request message comprising the payment account number;

sending, by the payment processor computer, the second authorization request message comprising the payment account number to the issuer computer;

receiving, by the payment processor computer, a second authorization response message comprising the payment account number from the issuer computer; and

sending, by the payment processor computer, a payment authorization message to the merchant.

13. The method of claim 1 wherein before the merchant-configured token format is received, a user affiliated with the merchant selects parameters for creating the merchant-configured token format and the graphical user interface displays a preview of an example token that has the merchant-configured token format.

14. The method of claim 1 wherein generating, by the payment processor computer, the token associated with the payment account number also comprises using a random number generator to generate a portion of the token.

16. The method of claim 14 wherein the portion of the token generated using the random number generator has no mathematical relation to the payment account number.

17. The method of claim 1 wherein the graphical user interface is configured to allow the merchant to specify the length of characters and character set used to generate tokens using the token format, wherein the merchant-configured token format specifies the length and characters of the tokens to be generated.

18. The method of claim 17 wherein the graphical user interface is further configured to allow the merchant to specify whether the tokens to be generated are generated by using only numbers, only letters, or only numbers and letters.

19. The method of claim 18 wherein the graphical user interface is further configured to allow the merchant to keep the last four digits of the payment account number in subsequently generated tokens or not keep the last four digits of the payment account number in subsequently generated tokens.

15. A payment processing computer comprising:

a processor; and

a non-transitory computer readable medium storing instructions, which when executed causes the processor to perform a method comprising

receiving via a graphical user interface on a merchant computer operated by a merchant, a merchant-configured token format from the merchant, wherein the graphical user interface is configured to allow the merchant to specify a length of characters or character set in the token format, wherein the merchant-configured token format specifies at least one of the length and characters of the tokens to be generated,

after receiving the merchant-configured token format, storing the merchant-configured token format received from the merchant in a database,

after the merchant-configured token format is stored, receiving from the merchant, a payment account number from a customer during a first transaction with the merchant,

generating or receiving an authorization request message comprising the payment account number,

sending the authorization request message comprising the payment account number to an issuer computer associated with the payment account number;

receiving an authorization response message comprising the payment account number from the issuer computer,

after receiving the authorization response message from the issuer computer, retrieving the merchant-configured token format from the database,

generating a token associated with the payment account number using the retrieved merchant-configured token format, the token including a set of characters, wherein the token conforms to the merchant-configured token format, and

sending to the merchant the token associated with the payment account number, wherein the token is stored at the merchant.

20. The payment processing computer of claim 15 wherein the graphical user interface is configured to allow the merchant to specify the length of characters and character set used to generate tokens using the token format, wherein the merchant-configured token format specifies the length and characters of the tokens to be generated.