SYSTEMS AND METHODS FOR TRANSMITTING FINANCIAL ACCOUNT INFORMATION

• US 20120078798A1
• Filed: 09/27/2010
• Published: 03/29/2012
• Est. Priority Date: 09/27/2010
• Status: Active Grant

• Current Assignee: Fidelity Information Services, LLC (Fidelity National Information Services Incorporated)
• Original Assignee: Fidelity National Information Services Incorporated
• Inventors: DOWNING, Robert W., Steffensmeier, Nicole
• Granted Patent: US 8,898,086 B2
• Time in Patent Office: Days
• US Class Current: 705/64
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/3827 Use of message hashing
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 63/0478 applying multiple layers of encryption, e.g. nested tunnels or encrypting the content with a first key and then with at least a second key cryptographic mechanisms or cryptographic arrangements using a plurality of keys or algorithms H04L9/14
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 9/3239 involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD

Abstract

Described herein are methods and systems for securely transmitting information, including financial account information. An irreversibly encrypted account number can be transmitted to a processing party as part of a transmission packet. The processing party can extract other information from the transmission packet to determine one or more registered account numbers that may match the irreversibly encrypted account number. Using the same encryption algorithm used to create the transmission packet, the processing party can create a verification packet by encrypting the one or more registered account numbers and determine if the verification packet matches the transmission packet. As a result, financial account information can be transmitted in such a way that it cannot be intercepted and then used to perform an unauthorized transaction.

Claims

1. A payment verification system comprising:

a database; and

a processor coupled to the database and configured to;

receive a transmission packet comprising an irreversibly encrypted account number;

select a registered account number from the database;

encrypt the registered account number in order to create a verification packet; and

determine if the verification packet matches the transmission packet.

2. The system of claim 1, wherein the transmission packet further comprises a client identification number.

3. The system of claim 2, wherein selecting the registered account number from the database is performed, at least in part, based on the client identification number.

4. The system of claim 1, wherein the transmission packet further comprises a reversibly encrypted portion of the account number.

5. The system of claim 4, further comprising:

decrypting the reversibly encrypted portion of the account number, and

wherein selecting the registered account number from the database is performed, at least in part, based on the decrypted portion of the account number.

6. The system of claim 1, wherein the transmission packet further comprises a random data string.

7. The system of claim 1, further comprising:

if the verification packet does not match the transmission packet;

selecting a second registered account number from the database;

encrypting the second registered account number in order to create a second verification packet; and

determining if the second verification packet matches the transmission packet.

8. A computer-readable storage medium containing instructions that, when executed by a processor, perform a method comprising:

concatenating an account number, a client identification number, and a random data string to create a combined data string;

creating an account signature comprising performing a hash operation on the combined data string;

transmitting the account signature, the client identification number, and a portion of the account number;

determining the account number using a database comprising a plurality of registered account numbers based on at least one of the portion of the account number, the client identification number, the account signature, and the random data.

9. The computer-readable storage medium of claim 8, wherein determining the account number comprises:

extracting the account signature, the random data, the client identification number, and the portion of the account number from the transmitted data;

identifying a registered account number in the database comprising the portion of the account number;

performing the hash operation on the registered account number, the random data, and the client identification number in order to create a test account signature;

determining if the test account signature matches the transmitted account signature.

10. The computer-readable storage medium of claim 8, wherein the encryption algorithm further comprises encrypting the account signature and the portion of the account number to create an inner packet.

11. The computer-readable storage medium of claim 10, wherein the encryption algorithm further comprises encrypting the account signature, the portion of the account number, and the client identification number to create an inner packet.

12. The computer-readable storage medium of claim 10, wherein creating the inner packet comprises encrypting the account signature, the portion of the account number, and at least one of a card type identifier, an email address, and an expiration date or time.

13. The computer-readable storage medium of claim 10, wherein the encryption of the inner packet is accomplished using a symmetric encryption algorithm.

14. The computer-readable storage medium of claim 10, wherein the encryption of the inner packet is accomplished using Base64 encoding.

15. The computer-readable storage medium of claim 10, wherein the encryption of the inner packet is accomplished using modified Base64 encoding.

16. The computer-readable storage medium of claim 10, wherein the encryption algorithm further comprises encrypting the inner packet and additional data to create an outer packet.

17. The computer-readable storage medium of claim 16, wherein the additional data comprises the client identification number.

18. The computer-readable storage medium of claim 16, wherein the encryption of the outer packet is accomplished using a symmetric encryption algorithm.

19. The computer-readable storage medium of claim 16, wherein the encryption of the outer packet is accomplished using an asymmetric encryption algorithm.

20. A method for decrypting information, comprising:

receiving encrypted data comprising an account signature, wherein the account signature comprises an irreversibly encrypted account number;

identifying the account signature;

retrieving a registered account number from a database;

encrypting the registered account number using an encryption algorithm;

determining if the output of the encryption algorithm matches the received encrypted data;

if the output of the encryption algorithm matches the received encrypted data, processing a payment using the registered account number.

21. The method of claim 20, further comprising receiving a client identification number.

22. The method of claim 20, further comprising receiving a portion of the account number.

23. The method of claim 20, wherein the encrypted data comprises a random data string.

24. The method of claim 21, wherein retrieving the registered account number is performed based, at least in part, on the client identification number.

25. The method of claim 22, wherein the registered account number comprises the portion of the account number.

26. The method of claim 20, further comprising receiving a client identification number, a portion of the account number, and a random data string.

27. The method of claim 26, wherein encrypting comprises encrypting the registered account number and at least one of the client identification number, the portion of the account number, or the random data string.

28. The method of claim 27, wherein the encryption algorithm comprises an irreversible secure hash algorithm.

29. The method of claim 28, wherein the irreversible secure hash algorithm is non-deterministic.

30. The method of claim 27, wherein the random data string is an 18 byte random data string.

31. The method of claim 26, wherein encrypting comprises:

concatenating the registered account number, the client identification number, and the random data string to create a combined data string;

performing a hash operation on the combined data string; and

concatenating the output of the hash operation and the random data string to create a new account signature.

32. The method of claim 24, wherein encrypting further comprises encrypting the new account signature, the client identification number, and the portion of the full account number.

33. The method of claim 27, further comprising, if the output of the encryption algorithm does not match the received encrypted data:

retrieving a second registered account number from the database;

encrypting at least the second registered account number using the encryption algorithm to obtain a second output of the encryption algorithm;

determining if the second output of the encryption algorithm matches the received encrypted data; and

if the output of the second encryption algorithm matches the received encrypted data, processing a payment using the second registered account number.

34. A keyless entry system comprising:

a database comprising a client identification number; and

a processor coupled to the database, configured to;

transmit a transmission packet comprising an irreversibly encrypted entry code and the client identification number;

increment the client identification number; and

store the incremented client identification number in the database.

35. The keyless entry system of claim 34, wherein the transmission packet further comprises a random data string.

36. The keyless entry system of claim 34, further comprising encrypting the entry code and the client identification number in order to create the transmission packet.

37. The keyless entry system of claim 34, wherein the entry code and the client identification number are irreversibly encrypted.

38. The keyless entry system of claim 35, wherein the entry code, the client identification number, and the random data string are irreversibly encrypted.

39. The keyless entry system of claim 34, further comprising:

a second database comprising a registered entry code and a registered client identification number; and

a second processor coupled to the second database, configured to;

receive the transmission packet;

encrypt the registered entry code and the registered client identification number to create a verification packet;

compare the transmission packet and the verification packet;

increment the registered client identification number; and

store the incremented registered client identification number in the second database.