METHOD AND SYSTEM FOR CORRELATING DIVERSE TRANSACTION DATA

• US 20170103387A1
• Filed: 11/17/2016
• Published: 04/13/2017
• Est. Priority Date: 06/06/2012
• Status: Active Grant

• Current Assignee: Lance Weber
• Original Assignee: Lance Weber
• Inventors: Weber, Lance
• Granted Patent: US 10,296,904 B2
• Time in Patent Office: Days
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/042 characterized in that the payment protocol involves at least one cheque
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/38 Payment protocols; Details thereof
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/383 Anonymous user system
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 2220/00 Business processing using cryptography postage metering system using cryptography G06Q2250/05
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/0207 Discounts or incentives, e.g. coupons or rebates
• CPC Class Codes: G06Q 30/0281 Customer communication at a business location, e.g. providing product or service information, consulting

Abstract

Embodiments of the present invention are directed to methods, systems, and apparatuses for matching e-commerce and physical point-of-sale transaction data. In one embodiment, a method includes receiving, by a computer, first transaction data comprising a payment token or second transaction data comprising a primary account identifier, wherein the payment token is derived from the primary account identifier, and providing, by the computer, a universal account identifier after receiving the payment token or the account identifier, wherein the universal account identifier is a substitute for the payment token and the primary account identifier.

Claims

1-20. -20. (canceled)

21. A computer system comprising:

one or more processors; and

a non-transitory computer-readable medium coupled to the one or more processors, the computer-readable medium comprising code executable by the one or more processors for performing a process comprising;

receiving transaction data for a transaction, the transaction data comprising a payment token;

determining a universal account identifier associated with the payment token, wherein determining the universal account identifier comprises;

sending a request message to a universal account identifier generator computer, the request message including the payment token;

receiving, by a merchant processor computer, and from the universal account identifier generator computer, a de-tokenization request message associated with the transaction, the de-tokenization request message including a tokenized version of a primary account identifier;

determining the primary account identifier associated with the transaction data;

generating a de-tokenization response message including the primary account identifier;

sending the de-tokenization response message to the universal account identifier generator computer, the de-tokenization response message including the primary account identifier; and

receiving the universal account identifier response message, the universal account identifier response message including the universal account identifier associated with the payment token, wherein the universal account identifier is generated based on the primary account identifier in the de-tokenization response message; and

processing the transaction using the transaction data and providing the universal account identifier to a merchant computer along with an authorization response message associated with the processing of the transaction.

31. A method comprising:

receiving transaction data for a transaction, the transaction data comprising a payment token;

determining a universal account identifier associated with the payment token, wherein determining the universal account identifier comprises;

sending a request message to a universal account identifier generator computer, the request message including the payment token;

receiving, by a merchant processor computer, and from the universal account identifier generator computer, a de-tokenization request message associated with the transaction, the de-tokenization request message including a tokenized version of a primary account identifier;

determining the primary account identifier associated with the transaction data;

generating a de-tokenization response message including the primary account identifier;

sending the de-tokenization response message to the universal account identifier generator computer, the de-tokenization response message including the primary account identifier; and

receiving the universal account identifier response message, the universal account identifier response message including the universal account identifier associated with the payment token, wherein the universal account identifier is generated based on the primary account identifier in the de-tokenization response message; and

processing the transaction using the transaction data and providing the universal account identifier to a merchant computer along with an authorization response message associated with the processing of the transaction.