Track data mapping system for processing of payment transaction data

Abstract

Systems and associated apparatuses and methods for processing payment transactions. A merchant's data processing system may provide payment transaction data in a first format (e.g., Track 1) to a payment processing network. The payment processing network may determine the issuer to which the data will be provided as part of a process for authorizing the payment transaction. It is determined if the issuer is one that is expecting or requires that the data be provided in a second format (e.g., Track 2). If the issuer is one that is expecting or requires that the transaction data be supplied in the second format, then it is determined if the issuer is enrolled in the appropriate data mapping service. If the issuer is enrolled in the data mapping service, then the inventive system performs the data mapping processes needed to provide the data in the second format to the issuer. The issuer may then use the received data to determine whether to authorize the payment transaction.

1 - 21 . (canceled) 
     
     
         22 . An apparatus for processing a payment transaction, comprising:
 an electronic processor programmed to execute a set of instructions;   a data storage device coupled to the processor; and   the set of instructions contained in the data storage device, wherein when the instructions in the set of instructions are executed by the processor, the apparatus processes the payment transaction by:   receiving an authorization request message for the payment transaction from a payment processing network, wherein the payment processing network previously determined an issuer for a payment account used for the payment transaction, determined that the issuer was enrolled in a transaction data mapping service, mapped data contained in the authorization request message from a first data format in which the data is provided in the authorization request message to a second data format, wherein the first data format is different than the second data format;   determining if the payment transaction is authorized; and   sending an authorization response message to the payment processing network.   
     
     
         23 . The apparatus of  claim 22 , wherein the first data format of the data is a Track 1 format and the second data format of the data is a Track 2 format. 
     
     
         24 . The apparatus of  claim 22 , wherein the payment processing network is configured to deliver authorization services and clearing and settlement services. 
     
     
         25 . The apparatus of  claim 22 , wherein the authorization response message is subsequently sent from the payment processing network to a merchant system. 
     
     
         26 . The apparatus of  claim 22 , wherein the payment processing network maps one or more of a primary account number (PAN), expiration date, service code, or PIN verification data in the authorization request message from the first data format to the second data format. 
     
     
         27 . The apparatus of  claim 26 , wherein the payment processing network further maps one or more of ATC or dCVV data in the authorization request message from the first data format to the second data format. 
     
     
         28 . The apparatus of  claim 27 , wherein the first data format is a Track 1 format, the second data format is a Track 2 format, and wherein the payment processing network further:
 maps the ATC or dCVV data to the discretionary data field of the Track 2 format by   (a) concatenating the data in field 11.2 of Track 1 to the data in field 11.1 of Track 1, with the data in field 11.2 preceding that of field 11.1;   (b) concatenating the result of (a) to the data in field 11.3 of Track 1, with the data obtained from (a) preceding that of field 11.3; and   (c) concatenating the result of (b) to the data in field 10.2 of Track 1, with the data obtained from (b) preceding that of field 10.2.   
     
     
         29 . A method comprising:
 receiving an authorization request message for the payment transaction from a payment processing network, wherein the payment processing network previously determined an issuer for a payment account used for a payment transaction, determined that the issuer was enrolled in a transaction data mapping service, mapped data contained in the authorization request message from a first data format in which the data is provided in the authorization request message to a second data format, wherein the first data format is different than the second data format;   determining if the payment transaction is authorized; and   sending an authorization response message to the payment processing network.   
     
     
         30 . The method of  claim 29 , wherein the first data format of the data is a Track 1 format and the second data format of the data is a Track 2 format. 
     
     
         31 . The method of  claim 29 , wherein the payment processing network is configured to deliver authorization services and clearing and settlement services. 
     
     
         32 . The method of  claim 29 , wherein the authorization response message is subsequently sent from the payment processing network to a merchant system. 
     
     
         33 . The method of  claim 29 , wherein the payment processing network maps one or more of a primary account number (PAN), expiration date, service code, or PIN verification data in the authorization request message from the first data format to the second data format. 
     
     
         34 . The method of  claim 33 , payment processing network further maps one or more of ATC or dCVV data in the authorization request message from the first data format to the second data format. 
     
     
         35 . The method of  claim 34  wherein the first data format is a Track 1 format, the second data format is a Track 2 format, and wherein the payment processing network further:
 maps the ATC or dCVV data to the discretionary data field of the Track 2 format by 
 (a) concatenating the data in field 11.2 of Track 1 to the data in field 11.1 of Track 1, with the data in field 11.2 preceding that of field 11.1; 
 (b) concatenating the result of (a) to the data in field 11.3 of Track 1, with the data obtained from (a) preceding that of field 11.3; and 
 (c) concatenating the result of (b) to the data in field 10.2 of Track 1, with the data obtained from (b) preceding that of field 10.2.