PROCESSING TRANSACTIONS OF DIFFERENT PAYMENT DEVICES OF THE SAME ISSUER ACCOUNT
First Claim
1. At each of a plurality of point of sale terminals (POS) of a merchant, for each of a plurality of consumers each seeking to conduct a transaction with the merchant for a good or service at a cost by using a payment device issued by an issuer in a payment system, a method comprising:
- reading data from a data storage region of the payment device that includes an identifier for an account assigned by the issuer of the payment device;
for each account, assigning a Globally Unique Identifier (GUID) to each unique said data read from the data storage region without information that changes with each said transaction; and
processing each said transaction to attribute each to;
a corresponding said account; and
the GUID within the corresponding said account.
1 Assignment
0 Petitions
Accused Products
Abstract
Each portable payment device associated with a single account within a payment processing system is distinguished using track data. The track data from the portable payment device is read at each of a plurality of merchant point of sale terminals (POS). Rather than relying on the PAN alone, a merchant may utilizes the track data, or a proxy thereof, as the unique identifier for the portable payment device. The merchant may then process transactions involving the portable payment device based on the unique identifier. For example, in the transit environment the transit fare for each rider with different portable payment devices but the same account can be calculated using the unique identifier, such as the full track data read from both tracks of the corresponding portable payment devices.
-
Citations
28 Claims
-
1. At each of a plurality of point of sale terminals (POS) of a merchant, for each of a plurality of consumers each seeking to conduct a transaction with the merchant for a good or service at a cost by using a payment device issued by an issuer in a payment system, a method comprising:
-
reading data from a data storage region of the payment device that includes an identifier for an account assigned by the issuer of the payment device; for each account, assigning a Globally Unique Identifier (GUID) to each unique said data read from the data storage region without information that changes with each said transaction; and processing each said transaction to attribute each to; a corresponding said account; and the GUID within the corresponding said account. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A method comprising:
-
receiving, for each of a plurality of access transactions, access transaction application data from a portable consumer device, wherein; the access transaction application data of each said portable consumer device has a predetermined data field configuration for use with a reader of an transit agency; the predetermined data field configuration of the access transaction application data includes a Primary Account Number (PAN) assigned by an issuer of the portable consumer device; assigning a Globally Unique Identifier (GUID) to each unique said access transaction application data having same said PAN, wherein the uniqueness is determined without information that changes with each said access transaction; processing the GUID of each said access transaction to attribute each said access transaction to; a corresponding said account; and the GUID within the corresponding said account. - View Dependent Claims (9, 10, 11, 12, 13, 14, 15)
-
-
16. At each of a plurality of transit system readers in a transit system, for each of a plurality of riders each seeking to conduct an access transaction for access to a facility of the transit system using a payment device issued by an issuer in a payment system, a method comprising:
-
reading data from a data storage region of the payment device, wherein; the data conforms to a magnetic stripe data (MSD) configuration in a track one/track two format; data in the track one/track two format includes; a Primary Account Number (PAN) determined by the issuer of the payment device and is statically stored in the payment device; and issuer discretionary data; for each PAN, assigning a GUID to each unique said data read from the data storage region without information in the issuer discretionary data that changes with each said access transaction; and processing the GUID of each said access transaction to attribute each said access transaction to; a corresponding said account; and the GUID within the corresponding said account. - View Dependent Claims (17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28)
-
Specification