IP Library Granted Patent US 11,328,300
Granted Patent B2
US 11,328,300 · App. 16/191,819 · Granted May 10, 2022

Enhanced security for transaction requests utilizing automatic source identification

Inventors: Robert J. Cole (Maysville, GA); Mary Januszka (Woodstock, GA); Alan Todd Blackburn (Dawsonville, GA); John J. Petrizzo (Marietta, GA); Robert J. Seitz (Lilburn, GA); Tim Seligman (Coral Springs, FL); Eric Stormo (Coral Springs, FL)
Assignee: FIRST DATA CORPORATION
G06Q20/4016G06F16/24G06F16/90335G06Q20/16G06Q20/202
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,328,300
App. No.
16/191,819
Granted
May 10, 2022
Kind
B2
Abstract

Described herein are methods and systems for enhancing security of transaction requests from POS terminals by utilizing ANI-DNIS information. The header of the transaction request can include automatic source information (“ASI”), which can be extracted from the header by the line handler. The ASI information can be provided to the front end interface, which can compare the ASI information with known customer information. The comparison can provide information indicating whether the transaction is legitimate or fraudulent. If fraudulent, the transaction request can be declined. The ASI information can further be stored in a security analysis database and further queried to identify larger threats including denial of service attacks.

Claims (99)

1. A transaction processing system comprising:

one or more processors; and

a memory having stored thereon instructions that, when executed by the one or more processors, cause the one or more processors to:

receive, from a point of sale device, a transaction request having a header and a first transaction level identifier;

determine that the header is a Source Information Header (“SIH”) comprising Automatic Source Identification (“ASI”) information;

extract the ASI information from the SIH;

generate a Fast Internal Message (“FIM”) comprising the ASI, wherein data within the FIM is standardized from multiple input and output formats into a single internal format;

identify a source sender and first source sender information from the FIM;

obtain second source sender information about the source sender from a database, the database containing client information;

generate a second transaction level identifier, the instruction to generate the second transaction level identifier comprising instructions that, when executed by the one or more processors, cause the one or more processors to:

identify a seed value based on the transaction request and a shared secret between the transaction processing system and the point of sale device,

generate a code based on the seed value, and

hash the code to generate the second transaction level identifier;

determine an approval status of the transaction request by:

declining the transaction request based on a determination that the first source sender information does not match the second source sender information,

declining the transaction request based on a determination that the first transaction level identifier does not match the second transaction level identifier, or

approving the transaction request based at least in part on a determination that the first source sender information matches the second source sender information and a determination that the first transaction level identifier matches the second transaction level identifier; and

store data from the FIM including the ASI in the database.

2. The transaction processing system of claim 1 , wherein the instructions comprise further instructions that, when executed by the one or more processors, cause the one or more processors to:

identify an expected source value from the second source sender information;

identify, from the ASI in the FIM, a source value of the transaction request; and

determine whether the first source sender information matches the second source sender information based on whether the expected source value matches the source value of the transaction request.

3. The transaction processing system of claim 1 , wherein the instructions comprise further instructions that, when executed by the one or more processors, cause the one or more processors to:

identify an expected transmission line for receiving the transaction request from the second source sender information;

identify, from the FIM, a transmission line on which the transaction request was received; and

determine whether the first source sender information matches the second source sender information based on whether the expected transmission line matches the transmission line on which the transaction request was received.

4. The transaction processing system of claim 1 , wherein the instructions comprise further instructions that, when executed by the one or more processors, cause the one or more processors to:

identify an expected message format for the transaction request from the second source sender information;

identify, from the FIM, a message format for the transaction request; and

determine whether the first source sender information matches the second source sender information based on whether the expected message format matches the message format for the transaction request.

5. The transaction processing system of claim 1 , wherein the ASI comprises an internet protocol (“IP”) address from which the transaction request originated.

6. The transaction processing system of claim 1 , wherein the ASI comprises a telephone number from which the transaction request originated.

7. The transaction processing system of claim 1 , wherein the instructions comprise further instructions that, when executed by the one or more processors, cause the one or more processors to:

store the ASI information in a security analysis database; and

identify fraudulent activity based on queries of the security analysis database.

8. The transaction processing system of claim 1 , wherein the point of sale device is a first point of sale device of a plurality of point of sale devices, and wherein the shared secret comprises a unique seed table shared only between the first point of sale device and the transaction processing system.

9. The transaction processing system of claim 8 , wherein:

identifying a seed value comprises selecting a seed entry from the unique seed table based on a timestamp associated with the transaction request.

10. A non-transitory, computer-readable medium having stored thereon instructions that, when executed by one or more processors, cause the one or more processors to:

receive, from a point of sale device, a transaction request having a header and a first transaction level identifier;

determine that the header is a Source Information Header (“SIH”) comprising Automatic Source Identification (“ASI”) information;

extract the ASI information from the SIH;

generate a Fast Internal Message (“FIM”) comprising the ASI, wherein data within the FIM is standardized from multiple input and output formats into a single internal format;

identify a source sender and first source sender information from the FIM;

obtain second source sender information about the source sender from a database, the database containing client information;

generate a second transaction level identifier, wherein the instructions to generate the second transaction level identifier comprise instructions that, when executed by one or more processors, cause the one or more processors to:

identify a seed value based on the transaction request and a shared secret with the point of sale device,

generate a code based on the seed value, and

hash the code to generate the second transaction level identifier;

determine an approval status of the transaction request by:

declining the transaction request based on a determination that the first source sender information does not match the second source sender information,

declining the transaction request based on a determination that the first transaction level identifier and the second transaction level identifier do not match, or

approving the transaction request based at least in part on a determination that the first source sender information matches the second source sender information and a determination that the first transaction level identifier matches the second transaction level identifier; and

store data from the FIM including the ASI in the database.

11. The non-transitory, computer-readable medium of claim 10 , wherein the instructions comprise further instructions that, when executed by the one or more processors, cause the one or more processors to:

identify an expected source value from the second source sender information;

identify, from the ASI in the FIM, a source value of the transaction request; and

determine whether the first source sender information matches the second source sender information based on whether the expected source value matches the source value of the transaction request.

12. The non-transitory, computer-readable medium of claim 10 , wherein the instructions comprise further instructions that, when executed by the one or more processors, cause the one or more processors to:

identify an expected transmission line for receiving the transaction request from the second source sender information;

identify, from the FIM, a transmission line on which the transaction request was received; and

determine whether the first source sender information matches the second source sender information based on whether the expected transmission line matches the transmission line on which the transaction request was received.

13. The non-transitory, computer-readable medium of claim 10 , wherein the instructions comprise further instructions that, when executed by the one or more processors, cause the one or more processors to:

identify an expected message format for the transaction request from the second source sender information;

identify, from the FIM, a message format for the transaction request; and

determine whether the first source sender information matches the second source sender information based on whether the expected message format matches the message format for the transaction request.

14. The non-transitory, computer-readable medium of claim 10 , wherein the ASI comprises an internet protocol (“IP”) address from which the transaction request originated.

15. The non-transitory, computer-readable medium of claim 10 , wherein the ASI comprises a telephone number from which the transaction request originated.

16. The non-transitory, computer-readable medium of claim 10 , wherein the instructions comprise further instructions that, when executed by the one or more processors, cause the one or more processors to:

store the ASI information in a security analysis database; and

identify fraudulent activity based on queries of the security analysis database.

17. The non-transitory, computer-readable medium of claim 10 , wherein the point of sale device is a first point of sale device of a plurality of point of sale devices, and wherein the shared secret comprises a unique seed table shared only with the first point of sale device.

18. A computer-implemented method comprising:

receiving, from a point of sale device, a transaction request having a header and a first transaction level identifier;

determining that the header is a Source Information Header (“SIH”) comprising Automatic Source Identification (“ASI”) information;

extracting the ASI information from the SIH;

generating a Fast Internal Message (“FIM”) comprising the ASI, wherein data within the FIM is standardized from multiple input and output formats into a single internal format;

identifying a source sender and first source sender information from the FIM;

obtaining second source sender information about the source sender from a database, the database containing client information;

generating a second transaction level identifier, the generating comprising:

identifying a seed value based on the transaction request and a shared secret with the point of sale device,

generating a code based on the seed value, and

hashing the code to generate the second transaction level identifier;

determine an approval status of the transaction request by:

declining the transaction request based on a determination that the first source sender information does not match the second source sender information,

declining the transaction request based on a determination that the first transaction level identifier does not match the second transaction level identifier, or

approving the transaction request based at least in part on a determination that the first source sender information matches the second source sender information and a determination that the first transaction level identifier matches the second transaction level identifier; and storing data from the FIM including the ASI in the database.

19. The computer-implemented method of claim 18 , further comprising:

identifying an expected source value from the second source sender information;

identifying, from the ASI in the FIM, a source value of the transaction request; and

determining whether the firsts source sender information matches the second source sender information based on whether the expected source value matches the source value of the transaction request.

20. The computer-implemented method of claim 18 , further comprising:

identifying an expected transmission line for receiving the transaction request from the second source sender information;

identifying, from the FIM, a transmission line on which the transaction request was received; and

determining whether the first source sender information matches the second source sender information based on whether the expected transmission line matches the transmission line on which the transaction request was received.

21. The computer-implemented method of claim 18 , further comprising:

identifying an expected message format for the transaction request from the second source sender information;

identifying, from the FIM, a message format for the transaction request; and

determining whether the first source sender information in the FIM matches the second source sender information based on whether the expected message format matches the message format for the transaction request.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 15, 2019
From: STORMO, ERIC G.
To: CARD ESTABLISHMENT SERVICES, INC.
Reel/Frame 051017/0693 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 15, 2019
From: CARD ESTABLISHMENT SERVICES, INC.
To: FIRST DATA CORPORATION
Reel/Frame 051017/0812 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 13, 2019
From: COLE, ROBERT J.; JANUSZKA, MARY; BLACKBURN, ALAN TODD; PETRIZZO, JOHN J.; SEITZ, ROBERT J.; SELIGMAN, TIM
To: FIRST DATA CORPORATION
Reel/Frame 050373/0597 →
Continuity (2)
Provisional Application 62587287 · Nov 16, 2017
Related Publication 20190147449A1 · May 16, 2019